DNS stops working intermittently for some clients. Ipconfig will f

[Guest]

All of my win2kpro and xpPro users are experiencing this. About once or
twice a day they will suddenly be unable to browse the internet. On
inspection we find that they can no longer resolve external ip-addresses. If
we run an ipconfig /renew or ipconfig /registerdns command they immediately
regain their external name resolution.
DNS servers are win2k servers active directory integrated DNS.
Does anyone have an explanation as to what may be going here ?

 

[Frankster]

Are you sure your clients are configured with ONLY your AD DNS servers?
Or... do they have a string of entries to include your ISP assigned DNS.

Most likely they are working until for some reason one name isn't resolved
and they switch to another DNS entry (probably a local one) and the local
one is root and reports back that "no such domain exists" (this is entirely
different than a simple "can not find" error). Since the DNS is root, it is
the final authority. If the root says it doesn't exist, it doesn't exist.
So it quits trying until you reestablish the sequence by rebooting or
release/renew. Then it all starts over again.

Most of the time the "fix" is to delete the "root" entry in your local DNS.
This will cause failed searches to be forwarded to the outside for
resolution.

Anyway, I rambled quite a bit. Does any of this make sense? Sorry, don't
have time right now to clean it up Just ask yourself if any of these
scenarios may apply to you. If not, ignore

-Frank

 

[Guest]

This may be a similar issue to what was suggested in the 'DNS Server' post of
4/20. I have my secondary DNS server configured to be the root dns server of
our ad domain. Because it is a root server it does not have the ability to
set up a forwarder server.
If a client uses the backup secondary dns server when it fails to get a
timely response from the primary, it would explain why all of a sudden they
are no longer able to resolve external host names.