Re: [dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations

2021-12-02 Thread Gregory Brzeski

Maybe allow users to set TTL on "domain" object in RIPE database?

Allowed values can be constrained to few common lengths of time? The 
default would be one decided here.


This way users would have a choice.

Gregory


On 02/12/2021 12:49, Tim Wicinski wrote:



I support lowering the TTL on the DS records to 3600.

I support lowering the TTL on the NS records - I was going to put my 
hat in for 21600,

but Mr van Dijk's suggestion of 3600 is very enticing.

But I liked Mr. Lawrence's suggestion on gathering data on lowering 
the NS records TTL.
Perhaps the TTL can be lowered from 172800 to 86400 to 21600, then to 
3600, collecting data

along the way.

tim


On Thu, Dec 2, 2021 at 6:35 AM Peter van Dijk 
 wrote:


On Mon, 2021-11-29 at 17:07 +0100, Ralf Weber wrote:
> Moin!
>
> On 29 Nov 2021, at 12:59, Anand Buddhdev wrote:
>
> > We propose to lower, in the first quarter of 2022, the TTL on
NS records to 86400 and on DS records to 3600.
> I very much support that and would go even lower for for NS
records. Maybe consider 21600 there.

Same. I support this, and I also support lowering NS even further,
even
to 3600.

Kind regards,
-- 
Peter van Dijk

PowerDNS.COM BV - https://www.powerdns.com/


-- 


To unsubscribe from this mailing list, get a password reminder, or
change your subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/dns-wg

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg


Re: [dns-wg] Lower TTLs for NS and DS records in reverse DNS delegations

2021-12-02 Thread Gregory Brzeski

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



--

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg