Resolv.conf not querying correctly?

Mark_Andrews at isc.org Mark_Andrews at isc.org
Thu Sep 30 22:27:49 UTC 1999


> In article <37F3A549.DC99861 at bork.net>, Bjarte Nilsen  <bork at bork.net> wrote:
> >Try to put the ip address of a non-nameserver first in your resolv.conf, and
>  run
> >nslookup -d2
> >
> >You'll see that it timeout 4 times first, before the next nameserver is quer
> ied.
> 
> As we told someone who asked almost the same question 2 days ago, nslookup
> doesn't use the same retry algorithm as the resolver library.  If you want
> to know what the resolver does, run tcpdump while you run a network
> application.

	Or with a modern resolver library "setenv RES_OPTIONS debug".

	Mark
> 
> -- 
> Barry Margolin, barmar at bbnplanet.com
> GTE Internetworking, Powered by BBN, Burlington, MA
> *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
> Please DON'T copy followups to me -- I'll assume it wasn't posted to the grou
> p.
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org


More information about the bind-users mailing list