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] RFC 7344 support in the RIPE database
- Previous message (by thread): [dns-wg] RFC 7344 support in the RIPE database
- Next message (by thread): [dns-wg] RFC 7344 support in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ondřej Caletka
Ondrej.Caletka at cesnet.cz
Mon Oct 22 16:40:19 CEST 2018
Dne 22.10.2018 v 15:58 Tony Finch napsal(a): > Yes, and it addresses Anand's comment that RIPE does not normally update > users' objects. But I'm a bit worried that it might be too obscure. If it > can't be eliminated entirely, perhaps it can be addressed by hints in the > web user interface? What about some semi-automated solution like this: 1. RIPE NCC would scan all the secure delegations for CDS records 2. if CDS is found and it differs from ds-rdata attribute in the database, then: 3a. if special maintainer is there, do the update 3b. if special maintainer in not there, send an e-mail to zone-c saying: "Hey, we've noticed you would like to change the DS records for your zone 2.0.192.in-addr.arpa. Please update your delegation in the RIPE database here (link). If you want to have updates done automatically, add this mnt-by: attribute to your domain object" -- Ondřej Caletka -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3718 bytes Desc: Elektronicky podpis S/MIME URL: </ripe/mail/archives/dns-wg/attachments/20181022/688a1718/attachment.p7s>
- Previous message (by thread): [dns-wg] RFC 7344 support in the RIPE database
- Next message (by thread): [dns-wg] RFC 7344 support in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]