[Dnsmasq-discuss] Cache Time Threshold

Robert Diamond deadram at gmail.com
Thu Apr 10 19:06:20 BST 2008

On Wed, 09 Apr 2008 19:36:20 +0100
Simon Kelley <simon at thekelleys.org.uk> wrote:

> My take on this is that the DNS admin set the Time-to-live, and it 
> shouldn't be over-ridden. If the DNS admin wanted a longer time, they 
> would have set it. Even if you get away with extending the TTL for
> most domains, eventually you'll find one which breaks.

dnsmasq could have a "keep-alive" cache, which updates cache entries
as they expire for a maximum time. Obviously set to something low,
1-10 keep-alive cache entries should be sufficient for most uses,
without ever using an expired ttl. ie: "--keep-alive-cache-count=3" and
"--keep-alive-cache-time=3600" would keep the last 3 cached dns
requests up to date for up to 1 hour past the last request for that

Robert A.M. Diamond
  <deadram at gmail.com>

"Anything created must necessarily be inferior to the essence of the
creator." -- Claude Shouse

"Einstein's mother must have been one heck of a physicist."
		-- Joseph C. Wang

More information about the Dnsmasq-discuss mailing list