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 ]

Gregory Brzeski gregory at brzeski.pl
Thu Dec 2 15:33:15 CET 2021

On 02/12/2021 14:46, Petr Špaček wrote:
>
> Why not make the TTL _dynamic_, based on time of last change in the 
> RIPE database?
>
I belive this is an interesting approach, however requires that same 
logic will be applied to all users on server side.

The question arises if same logic fits all users.

When TTL can be set by a user on "domain" object in RIPE database then 
this logic is controlled by a user, what allows different users to have 
different strategies, allowing for flexible approach.

Gregory Brzeski

• 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 ]