[dns-wg] Retiring ns.ripe.net

Dear colleagues,

Thank you for the feedback we received on our proposal to retire the
ns.ripe.net service, as detailed in the RIPE Labs article published on
2 May. Your input on the mailing list and at the DNS Working Group
session at RIPE 88 helped us see if there were any problems with our
approach.

After reviewing the mails and hearing feedback at the Working Group
session, we have general agreement for the move and have decided to go
ahead with the proposed plan with some amendments to the timeline.

We have updated the RIPE Labs article with our amended timeline:
https://labs.ripe.net/author/anandb/retiring-nsripenet/

As always, if you have any further thoughts or suggestions, please let
us know on the list.

Best regards,

Paul de Weerd
Manager Global Information Infrastructure team
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