Posting the dnsreport.com output helps a lot. I readily admit I had not seen the missing nameserver “stealth” stuff on a report before, and I don’t fully understand what is going on with that (off to Google to learn!).
However, I happened to be on the dreamhost irc channel (freenode #dreamhost) where some “wizards” hang out, and passed the url to your dns report to them. One of the “wizards” took a look at it and said he knew what the problem was. According to him:
" that is kinda wierd…check the zones file at your new DNS host…wait…I KNOW… the glue is out of rate… you’ll have to email the registar to change the glue… The Name Server names in the whois are just cosmetic, and some RFC thing… Basically, when you request dns stuff, it will ping the DNS servers, and it will go step by step to get the Zone server… using ip addresses, so it will take the glue etc, which is DH in this case… Basically it saves another set of NS lookups… The registrars are the only people that can touch it, from memory… It depends on the tld policies etc… took me a couple of moments to realise what was up, but we got there!"
(That is a “cut-n-paste” of “his” side of the conversation, editing out the misc non-relevant traffic on the channel.)
I have to do a little more research on “glue” to understand what he is saying at the level I want to understand it, but I wanted to pass this on as he very clearly understood from looking at the report what seemed to be the problem, and I have been impressed with his knowledge in other situations.
Of course, all the standard disclaimers apply, YMMV, etc. - but I think this indicates it is time for a contact with the registrar about the issue. It probably couldn’t hurt to file a DH support ticket (if they can manually remove the entry from their nameserver(s) and/or tweak the TTL?), but it may very well be totally under the control of the registrar.
Hope this helps! Good luck, and please let us know what you learn, as this is an unusual situation.