+27 November 2007: Wouter
+ - per suggestion in rfc2308, replaced default max-ttl value with 1 day.
+
22 November 2007: Wouter
- noted EDNS in-the-middle dropping trouble as a TODO.
At this point theoretical, no user trouble has been reported.
# the time to live (TTL) value cap for RRsets and messages in the
# cache. Items are not cached for longer. In seconds.
- # cache-max-ttl: 864000
+ # cache-max-ttl: 86400
# the time to live (TTL) value for cached roundtrip times and
# EDNS version information for hosts. In seconds.
Must be set to a power of 2.
.It \fBcache-max-ttl:\fR <seconds>
Time to live maximum for RRsets and messages in the cache. Default is
-864000 seconds (10 days). If the maximum kicks in, responses to clients
+86400 seconds (1 day). If the maximum kicks in, responses to clients
still get decrementing TTLs based on the original (larger) values.
When the internal TTL expires, the cache item has expired.
Can be set lower to force the resolver to query for data often, and not
cfg->host_ttl = 900;
cfg->lame_ttl = 900;
cfg->bogus_ttl = 900;
- cfg->max_ttl = 3600 * 24 * 10;
+ cfg->max_ttl = 3600 * 24;
cfg->infra_cache_slabs = 4;
cfg->infra_cache_numhosts = 10000;
cfg->infra_cache_lame_size = 10240; /* easily 40 or more entries */