[TriLUG] Re: DNS lookup of Linux server fails intermittently (OT - W2K and DNS)

Geoffrey Douglas Purdy gdpurdy at unity.ncsu.edu
Mon Dec 3 13:33:19 EST 2001


Jeremy,

Thanks for the clarification.  I got the general point that the problem is
caused by the W2K clients being given a set of nameservers containing
both internal and external DNS servers.  The solution would be to hand the
client only a set of internal DNS servers and instruct the internal DNS
servers to forward requests to the external DNS servers when necessary.

(Fortunately) implementing this on the W2K DNS and DHCP servers is the
turf of our Windows sysadmin.  He's made the changes to DHCP such that
clients only get a list of internal DNS servers.  At this point, it's
pretty much wait and see if the problem goes away.  The old DNS info
should be purged from all clients in three days (the length of leases) or
less.

I will be very glad if we can demonstrate that this is not related to the
fact that we're running a Linux webserver.  I mentioned in another
message that this is our first major deployment on a Linux platform.  As
one might anticipate, the Windows admins tend to immediately blame
problems on Linux whenever possible.

Thanks again for your help,

Geoff




More information about the TriLUG mailing list