Quote:
|
Originally Posted by Taf
...and decided not to automatically blame NTL...
|
Why not? In my experience it's usually their fault
I found article 331880 on the Microsoft support site. Is that the one you meant? It relates to DNS client-side caching, and explains how to turn it off or change the cache time.
It looks like the client DNS cache is a mechanism that locally stores the results of a successful DNS query and reduces the number of DNS lookups that the client has to request because, having cached the results of a DNS query, it can just fetch it from memory instead.
The default cache time appears to be 86,400 seconds (1 day). I was seeing intermittent problems where a site would respond OK and then not respond a few seconds later. Given the short-term intermittent nature of the problem, I doubt that client DNS cacheing was to blame, but if the fault comes back I'll give it a try
Mike