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] Using CDS delegation to add DS records (was Re: NCC reverse delegation criteria)
- Previous message (by thread): [dns-wg] Using CDS delegation to add DS records (was Re: NCC reverse delegation criteria)
- Next message (by thread): [dns-wg] Using CDS delegation to add DS records (was Re: NCC reverse delegation criteria)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erwin Lansing
erwin at dk-hostmaster.dk
Tue Jun 11 09:00:39 CEST 2019
> On 10 Jun 2019, at 18.04, Shane Kerr <shane at time-travellers.org> wrote: > > > > Of course, if the goal was ADDING of DS records, then I admit that the system is not there. I can see the benefit of being able to add DS records to the parent via CDS/CDNSKEY, especially for operators trying to secure (for example) reverse DNS for lots of /24's. > > Is this important to you (or anyone else)? > I’ll raise my hand here. We hold a legacy PI /24, which means the parent, in the DNS sense, is run by a 3rd party, not us nor RIPE. Of course that 3rd party does not support DNSSEC, at least last time I asked. Med venlig hilsen / Best regards Erwin Lansing Head of Security & Chief Technologist
- Previous message (by thread): [dns-wg] Using CDS delegation to add DS records (was Re: NCC reverse delegation criteria)
- Next message (by thread): [dns-wg] Using CDS delegation to add DS records (was Re: NCC reverse delegation criteria)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]