| UBC Physics & Astronomy
Windows 2000/XP DNS Cache Issue |
By default, the DNS Client service ("Dnscache") is enabled on Windows 2000/XP, so DNS lookups are cached locally for a certain period of time - set by TTL (time-to-live). This speeds up the process of looking up domain names. Windows 2000/XP caches successful ("positive") DNS lookups, and also unsuccessful ("negative") DNS lookups. The downside is during TTL, if an IP for an URL changes, problem occurs.
PHAS Windows 2000/XP users are experiencing intermittent connection timeouts and failures. Since disabling "negative" DNS caching does not work, the next step is to disable the DNS Client service.
According to Microsoft, if the DNS Client service is turned off, the computer can still resolve DNS names by using the network's DNS servers. See http://support.microsoft.com/kb/318803
Nscd is a *nix daemon that caches DNS lookups. The configuration file, /etc/nscd.conf, determines the behavior of the cache daemon. By default, nscd daemon is disabled (Could someone please confirm this? Thanks!). That's why *nix systems do not experience the same DNS lookups issue as Windows 2000/XP (Feel free to expand on this).
Disabling the DNS Client service on Windows 2000/XP:
Disabled the DNS Client service ("Dnscache") on the following workstations:
Reference(s):
DNS Resolver Cache
How to Disable Client-Side DNS Caching in Windows XP and Windows Server 2003
nscd(8): name service cache daemon
How to flush DNS cache in Linux / Windows / Mac
Oliver Sturm's weblog - The DNS Client service riddle
The Elder Geek - DNS Client Service
| Tom | 2007-01-10 |