What about using a CNAME for the machine that it is hosted on? [just replying to the topic in general, no one specifically]
The "funny" thing is that Jay at Dreamhost said it was fine "You can point your domain to the IP address of the Dreamhost nameservers, this wil work the same way as changing the nameservers."
However, I think Jay may be mistaken here since the name servers do not respond on port 80. But at least he said it was no problem.
I presume that if you were switching servers there would be some type of notice since if you have shell access you are ftp-ing into that host?
I'd prefer to use other name servers for many reasons, including:
1. They have many redundant name servers
2. Huge capactiy
3. Distributed (geographically-power and connectivity) servers
4. since I have seen a fair number of filer issues, network storage issues etc (plus the issues of the Comcast and AOL blocks), I'd prefer to avoid machines subject to that. (As I said, FTP, mail etc do not matter - hosting is my only requirement).
Likewise from a management perspective it is much easier to have all our names using the same name servers instead of having any odd ones.
I am going to try a CNAME or A record for the host and see if that resolves correctly.