Re: timeouts and negative caching

Hi, > Where do these 300 seconds come from and how can I configure them? I'd like > to drastically reduce them to something like 10 seconds or so to make sure > bind retries to resolve a query shortly after a timeout. I've upgraded my bind version to 9.10.2 and there this timeout-ttl is set to 1

Re: timeouts and negative caching

Hi Tony, > Look at the lame-ttl option. (though I think the behaviour is more > complicated than the documentation implies) I can report that lame-ttl doesn't help either, the timeout ttl stays at 300 secs. >From reading the manual it seems to me that a "lame server" is something different th

Re: timeouts and negative caching

Hi Mike, On Thursday 11 June 2015 14:37:11 you wrote: > I'm not sure if BIND has a separate tunable for the "timeout vs true > negative answer" scenario you seem to describe, but have you tried setting > max-ncache-ttl very low to see if it affects this? just tried it: max-ncache-ttl doesn't seem

timeouts and negative caching

Hi, I've got a bind running as recursive resolver behind a thin internet line. When the line is clogged, requests sometimes time out. When the dns client retries the query, bind usually retries the request and eventually succeeds. So far so good. But now I sometimes see that bind does not retr