Name resolution failure on a caching server -- many '; pending-answer' records in the cache

Dear All, I run a caching server on a section of the departmental LAN. Occasionally network congestion results in timeouts & name resolution failures. Lookups performed on name servers outside my LAN section fail with NXDOMAIN. Querying my name server for items not in its cache gets the same

Re: Name resolution failure on a caching server -- many '; pending-answer' records in the cache

Thanks for the followup. > > NXDOMAIN is not a "failure" response. Are you *sure* you're getting NXDOMAIN? Yes. Pretty sure. With hindsight I should have run the tests inside a 'script' session. > If you're using nslookup to test, be aware that it will do suffix searching > by default, so if