Free Thinking

Kevin Darcy kcd at daimlerchrysler.com
Wed Aug 30 22:39:34 UTC 2000


Quadri, Jay wrote:

> Why is it that when nslookup is used, the resolver does not move to the next
> nameserver in the resolv.conf to query it, it only does so if you set server
> option.  I would have thought it'll be dynamic.

Automatic failover is not appropriate for a troubleshooting tool, in my
opinion. I want to know *exactly* what nameserver my DNS troubleshooting tool
is querying at all times; the fact that it uses the system resolver
configuration at all is merely a convenience I can live with, but I think
automatic failover would confuse and complicate the task of troubleshooting
DNS.

> Also the Windows resolver
> seems to be slightly different to Solaris.  The windows one is more forgiven
> in treading down the DNS search list  (not with nslookup, but with things
> like pinging etc.)

Hopefully, not so "forgiven" as to create the security problem described in
RFC 1535...

> Another question, do you know what the contents of the named.root file on
> A.ROOT-SERVERS.NET server on Internic.  I guess it would be the same
> named.root file used everywhere on the Internet.

By "named.root" I assume you mean a hints file (I've never used the
"standard" naming conventions)? A server that's authoritative for the root zone
has no need of such a thing.


- Kevin




More information about the bind-users mailing list