Weird question.

[Jobe Bittman]

I can't query my own server for NS RRset because it believes it has 
authority for domains that customers have moved and never told us they 
moved. I cannot trust my server so I would have to query someone else's 
name server. Also, the NS records could be wrong. For example, you slave a 
bunch of domains before a transfer then change them to masters in 
named.conf afterwards and forget to change the NS records when you update 
the zone. Not that I ever did that before... You are correct there is no 
reason to overload the whois servers. But how do I verify that the NS 
record is correct? Is there a way to query the root servers to validate the 
NS record? How?

>         Why over load the whois servers.
>
>         It's easy enough to compute the parent zone the ask its servers
>         for the NS RRset for the child zone.  It should also be faster.
>         It also works for ALL zones.
>
>         This will supply you with a list of zones that may need further
>         investigation.
>
>         Mark
>--
>Mark Andrews, Internet Software Consortium
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org