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/[email protected]/
[dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations
- Previous message (by thread): [dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations
- Next message (by thread): [dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Ebersman
list-ripe-dns-wg at dragon.net
Thu Dec 2 17:28:20 CET 2021
gregory> Maybe allow users to set TTL on "domain" object in RIPE gregory> database? Be nice if we could expand to a more sane/standard set of TTLs for NS/DS in TLD/SLDs, which makes this non-functional for a slew of such zones. gregory> Allowed values can be constrained to few common lengths of gregory> time? The default would be one decided here. I made this same comment during the recent DNS-OARC. There is value in a somewhat longer TTL for steady state, to weather temporary glitches in routing (though current values are way too long for even that). When doing provider changes and/or KSK rollovers, a shorter value makes more sense. I think with some testing and actual data, we can come up with a short list of useful values without having to allow unconstrained, random user-picked values that will just create support issues and not really improve the situation.
- Previous message (by thread): [dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations
- Next message (by thread): [dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]