From: Jonathan Williams (jonathw@shubertorg.com)
Date: Fri Jun 27 2003 - 12:02:41 EDT
Ok. I've got one alphaserver (tru64 5.1a) here configured as a master DNS
server, and another (tru64 5.1b) configured as a slave DNS server. Today we had
to bring the master server offline for a while, and when we did this we noticed
some DNS issues cropped up.
All of our other servers (running tru64 5.1b patchkit 2) are clients of these
two DNS servers. One would assume that if the master is offline, then the
clients would just go to the slave for name resolution. Well...it does do that,
but there is a HUGE delay (about a minute maybe) when you do an nslookup (for
example). And after that delay it will tell you that the attempt to connect to
the master server timed out, and then the response from the slave server comes
right up. But this happens everytime you try to do any DNS lookups...not just
the first time. We went and took out the master server from the list of DNS
servers for the clients, and then everything worked fine.
So my question is, are there any tweakables for this sort of thing? Can I
shorten the timeout period, or something like that? I went through the Network
Administration: Services guide...but couldn't really find any configuration
files that might effect this. Thanks in advance. =)
Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:25 EDT