> On Dec 1, 2017, at 11:38 AM, Ólafur Guðmundsson <ola...@cloudflare.com> wrote: > > > I strongly disagree with your "terminology", TTL is a hint about maximum > caching period, not a demand or a contract. > A resolver can at any time for any reason discard cached entries.
Agreed. > Many Authoritative operators have "unreasonable" TTL's like less than 10 > seconds or multiple days and I see no reason why resolvers do not > apply minimal and/or max caching rules that are reasonable. Yes, I remember a load balancer from the last century that had serious issues with DNS requests with low TTLs. We ended up replacing it. TTL is certainly a MAX, but no reason you can’t return a shorter value. My stub resolver may see a lower number if an item is about to be evicted from cache, should we not see that? Clamping the max seems helpful and causes the least enduser harm, so is quite wise. The same would be true hitting a large anycast dns server like 75.75.75.75 or 8.8.8.8, 4.2.2.1, you may hit a different backend for whatever reason so see varying TTLs for the same query within a 10 second interval based on that. That’s not bad, it’s working as designed. I think measurements are interesting though, so identifying TTL clamping in the wild would be an interesting study. - jared _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
