[dns-wg] Migration of ns.ripe.net to new IP addresses

Dear colleagues,

The RIPE NCC allows users to use ns.ripe.net as a secondary DNS server
for reverse zones of /16 IPv4 and /32 IPv6 address space. This name
server has had the addresses 193.0.0.193 and 2001:610:240:0:53::193 for
several years.

We are now migrating all the secondary zones on this server to a new,
modern cluster of servers. For this, we have to assign new addresses to
ns.ripe.net. These new addresses will be:

193.0.9.6
2001:67c:e0::6

We will change the addresses tomorrow, 13 March. The TTL of the address
records is currently six hours, so we expect that most DNS clients will
be talking to the new server by the next morning.

This change has one important consequence as far as NOTIFY messages are
concerned. Our new DNS cluster is in an anycast prefix, so we do not
transfer zones directly to any server in the cluster. We transfer zones
to our provisioning server, and then transfer them to the cluster. If
you wish to use DNS NOTIFY, please add the following IP addresses of our
provisioning server to your notify list and allow zone transfers to
these addresses:

193.0.0.198
2001:67c:2e8:5:53::6

If you do not send NOTIFY messages to our provisioning server, the
zones will be refreshed based on the refresh timer in the SOA record of
the zone.

Finally, I would like to take this opportunity to remind users that the
use of ns.ripe.net as a secondary server is not mandatory. You do not
have to use it. If you have good DNS infrastructure and do not require
ns.ripe.net as a secondary, you may remove it from your zone and from
the domain object of that zone in the RIPE Database.

If you have any other questions about this change of addresses, please
send email to <dns at ripe.net>.

Regards,

Anand Buddhdev
RIPE NCC