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] Sunsetting ns.ripe.net - new domain objects can no longer reference ns.ripe.net
- Previous message (by thread): [dns-wg] Retiring ns.ripe.net
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul de Weerd
pdeweerd at ripe.net
Tue Jun 18 13:31:24 CEST 2024
Dear colleagues, On 6 June, we announced an updated schedule for the retirement of the "ns.ripe.net" secondary DNS service for LIRs. In this updated schedule, the first step was to stop accepting delegation requests with the name server "ns.ripe.net" in them. We have therefore adjusted our reverse DNS checking process to reject new delegation requests with "ns.ripe.net". If you are using this secondary service, you may also begin an orderly transition away from it, by updating the NS records in your zones, and then updating your domain objects in the RIPE Database, to remove "nserver" attributes containing "ns.ripe.net". Later this week, we will send out emails to users of the service, with a link to our RIPE Labs article, and instructions for stopping the use of this service. If you have any questions, please email dns at ripe.net. Regards, Paul de Weerd Manager Global Information Infrastructure team RIPE NCC
- Previous message (by thread): [dns-wg] Retiring ns.ripe.net
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]