Long time getting to secondary server

Barry Margolin barmar at bbnplanet.com
Wed Jan 5 23:20:47 UTC 2000


In article <3873A376.77200AD4 at ncdc.noaa.gov>,
Doug Snowden  <dsnowden at ncdc.noaa.gov> wrote:
>If I kill named on my primary server (IBM) and
>do an nslookup on another machine it takes about
>70 seconds to get to the secondary server. The secondary server does
>finally return the results.
>This is true on both IBM and Sun machines. I
>have both machines in the resolv.conf file.
>What is going on. Obviously a timeout, but I thought the timeout was
>supposed to be about 5 seconds? Is there somewhere to set this timeout?
>Did I expain this well enough?

nslookup does things in a different order than the resolver does.  It tries
the first server multiple times before going to the second server.  The
resolver tries each server once, then tries them each with a longer
timeout.

-- 
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 group.



More information about the bind-users mailing list