[dns-wg] Retiring ns.ripe.net

Dear colleagues,

Let me start by thanking you for the feedback so far on our proposal
to retire the ns.ripe.net service, as detailed in the RIPE Labs
article we published last week. Your input helps us better understand
the needs and requirements of the membership and the larger community.
We acknowledge the concerns raised about the planned time for actually
shutting down the service and want to address them here.

First, if the members reach consensus on the proposal and we decide to
shut down the service, we will work hard to ensure all users are
migrated before the end of 2024. When everybody has moved away, we can
safely take down the service. But in the case where there are still
zones actively (and correctly) being served from ns.ripe.net, we will
not take the service down during the end-of-year freeze that many
organisations observe, instead postponing that for a few days into
January. We will provide a more precise timeline with the exact date
of service end if we decide to go ahead with our proposed plan.

I hope this covers the concerns raised. If you have any further
thoughts or suggestions, or want to advocate for keeping the service
running, please share your thoughts on the list!

Best regards,

Paul de Weerd
RIPE NCC

On Thu, 2 May 2024 at 17:49, Paul de Weerd <pdeweerd at ripe.net> wrote:
>
> Dear colleagues,
>
> We have published a RIPE Labs article on how we believe it is now time
> to retire the secondary DNS service for member’s reverse DNS
> delegations, ns.ripe.net:
> https://labs.ripe.net/author/anandb/retiring-nsripenet/
>
> We are proposing to retire the secondary DNS service by the end of
> 2024 and we're asking for your input and feedback on this proposal.
> Please share any feedback on the DNS Working Group mailing list by 16
> May 2024.
>
> Once we’ve collected your feedback, we will discuss this topic in the
> DNS Working Group session at RIPE 88 on Wednesday, 22 May 2024.
>
> Paul de Weerd
> Manager Global Information Infrastructure team
> RIPE NCC