<div dir="ltr"><div class="gmail_default" style="font-family:monospace">Thanks Shane</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Before I wrote that I went and dug around looking for examples....and looking at your link I know what I did. I was reading the max-ncache-ttl setting. DOH and double DOH.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">I am chastised and thanks!<br><br></div><div class="gmail_default" style="font-family:monospace">tim</div><div class="gmail_default" style="font-family:monospace"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 29, 2024 at 4:09 PM Shane Kerr <<a href="mailto:shane@time-travellers.org">shane@time-travellers.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Tim,<br>
<br>
On 24/03/2024 20.00, Tim Wicinski wrote:<br>
> Some more and apologies as I was thinking the updates were in the git <br>
> repo which was what confused me.<br>
> <br>
> <br>
> ### TTL Recommendations<br>
> <br>
> Software typically defaults to a maximum stored TTL of 1 or 2 days.<br>
> A lower TTL will mean removing rarely-used records that have long TTL,<br>
> and should not have much operational impact from a CPU or network<br>
> point of view<br>
> <br>
> Where did this 1 or 2 days come from? From most s/w I've seen the default<br>
> max-cache-ttl is a few hours.<br>
<br>
For defaults...<br>
<br>
It came from a vague memory of mine from a DNS OARC presentation in the <br>
mists of history. I recall some presentation where someone measured this <br>
and found that most cache entries disappeared after 1 day, and <br>
everything else except for a rounding error after 2 days. Neither <br>
DuckDuckGo nor Qwant seem to be able to help me find said presentation, <br>
so it might be a LLM-style hallucination in my brain.<br>
<br>
I did check defaults from various open source resolvers:<br>
<br>
BIND uses 1 week:<br>
<br>
<a href="https://bind9.readthedocs.io/en/stable/reference.html#namedconf-statement-max-cache-ttl" rel="noreferrer" target="_blank">https://bind9.readthedocs.io/en/stable/reference.html#namedconf-statement-max-cache-ttl</a><br>
<br>
Unbound uses 1 day:<br>
<br>
<a href="https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html" rel="noreferrer" target="_blank">https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html</a><br>
<br>
Knot Resolver uses 1 day:<br>
<br>
<a href="https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-cache.html#cache.max_ttl" rel="noreferrer" target="_blank">https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-cache.html#cache.max_ttl</a><br>
<br>
PowerDNS Recursor uses 1 day:<br>
<br>
<a href="https://doc.powerdns.com/recursor/settings.html#max-cache-ttl" rel="noreferrer" target="_blank">https://doc.powerdns.com/recursor/settings.html#max-cache-ttl</a><br>
<br>
Cheers,<br>
<br>
--<br>
Shane<br>
</blockquote></div>