This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] [Ext] Re: Changes to Time-to-Live (TTL) values in reverse DNS zones
- Previous message (by thread): [dns-wg] [Ext] Re: Changes to Time-to-Live (TTL) values in reverse DNS zones
- Next message (by thread): [dns-wg] [Ext] Re: Changes to Time-to-Live (TTL) values in reverse DNS zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dave Lawrence
tale at dd.org
Thu Apr 21 20:57:19 CEST 2022
Edward Lewis writes: > > Unrelated, or just less correlated than you might otherwise imagine? > > Unrelated. > > I'd studied an event which made it apparent that resolvers vastly > ignored the long TTLs in play. At the time I learned that two > popular strains of resolver code had an "internal" limit on the TTL > they would accept [which is old news now], meaning any authoritative > server operator who was banking on long TTLs to lower traffic was > not going to realize any benefit. The "ignored the long TTLs" goes right to the heart of the question though. If you tell me something akin to "it looks like TTLs under six hours impact query refresh rate but then starts a rapid decline to where almost no TTLs are honored for longer than 24 hours" then I'd say that does not indicate TTLs and traffic are unrelated, just related in a smaller window than those favoring long TTLs would hope. Conditional correlation != unrelated.
- Previous message (by thread): [dns-wg] [Ext] Re: Changes to Time-to-Live (TTL) values in reverse DNS zones
- Next message (by thread): [dns-wg] [Ext] Re: Changes to Time-to-Live (TTL) values in reverse DNS zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]