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

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

NXDOMAIN is not a "failure" response. Are you *sure* you're getting NXDOMAIN? If you're using nslookup to test, be aware that it will do suffix searching by default, so if the original query, e.g. www.bbc.co.uk fails, it'll quietly (unless debug-mode is in effect) start appending suffixes. Look