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] follow up of "Update RIPE's DNS Zonemaster"
- Previous message (by thread): [dns-wg] follow up of "Update RIPE's DNS Zonemaster"
- Next message (by thread): [dns-wg] follow up of "Update RIPE's DNS Zonemaster"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Cao
nickcao at nichi.co
Sat Feb 19 10:54:33 CET 2022
Strangely, after leaving everything as-is for a day, the rollover has been completed automatically. Guess that it was the mechanism documented in https://www.ripe.net/manage-ips-and-asns/db/support/configuring-reverse-dns#4--automated-update-of-dnssec-delegations taking effect. However, the same checks would have been applied to this procedure, or was the system using another instance of zonemaster or other software? On 2/18/22 21:41, Nick Cao via dns-wg wrote: > When doing a DNSSEC algorithm rollover from ecdsap256sha256 to ed25519 > today, I got the error 'Unknown cryptographic algorithm' when updating > ds-rdata field. A quick google search led me to > https://www.ripe.net/ripe/mail/archives/dns-wg/2021-January/003796.html, > which dates back to more than a year ago. It seems that the zonemaster > deployment has not been updated to day, thus I would like to ask about > the current progress. >
- Previous message (by thread): [dns-wg] follow up of "Update RIPE's DNS Zonemaster"
- Next message (by thread): [dns-wg] follow up of "Update RIPE's DNS Zonemaster"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]