You are here: Home > Participate > Policy Development > Policy Proposals > Change in IP Assignments for Anycasting DNS Policy

Change in IP Assignments for Anycasting DNS Policy

Current:

(from ripe-405):

6.9 Anycasting TLD Nameservers

If the name server set of a ccTLD or a gTLD without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD administrator may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

The prefix will be assigned by the RIPE NCC directly to the TLD, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer.

(from ripe-388):

7. Assignments for Anycasting TLD Nameservers

If the name server set of a ccTLD or a gTLD without anycasting technology applied would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the TLD administrator may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

The prefix will be assigned by the RIPE NCC directly to the TLD, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database and must be returned to the RIPE NCC if not in use for anycast DNS any longer.


New:

(For IPv4)

6.9 Anycasting Name servers

If the name server set of an organisation running DNS without using anycasting technology would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the organisation may receive a single dedicated /24 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

The organisation should demonstrate that the number of name servers or IP addresses for these name servers in the delegation exceeds eight and that without anycasting their zone size exceeds the UDP datagram size.

The organisation should also demonstrate that they need to do anycasting due to the geographical diversity of their DNS setup. The organisation will be required to demonstrate that anycasting will be used in diverse geographical locations. The existence of the real servers should be demonstrated with anycasting nodes that can be pinged and tracerouted.

The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database. The prefix must be returned to the RIPE NCC if no longer in use for anycast DNS.

(For IPv6)

7. Assignments for Anycasting Name servers

If the name server set of an organisation running DNS without using anycasting technology would not pass the 'IANA Administrative Procedure for Root Zone Name Server Delegation and Glue Data' the organisation may receive a single dedicated /48 network prefix for the sole purpose of anycasting name servers, as described in RFC 3258.

The organisation should demonstrate that the number of name servers or IP addresses for these name servers in the delegation exceeds eight and that without anycasting their zone size exceeds the UDP datagram size.

The organisation should also demonstrate that they need to do anycasting due to the geographical diversity of their DNS setup. The organisation will be required to demonstrate that anycasting will be used in diverse geographical locations. The existence of the real servers should be demonstrated with anycasting nodes that can be pinged and tracerouted.

The prefix will be assigned by the RIPE NCC directly to the organisation, upon a request submitted via an existing LIR and will be registered with a status of 'ASSIGNED ANYCAST' in the RIPE Database. The prefix must be returned to the RIPE NCC if no longer in use for anycast DNS.

Get Involved

The Address Policy Working Group develops policies relating to the allocation and registration of Internet number resources (IPv4 and IPv6 addresses and ASNs) by the RIPE NCC and its members. Anyone with an interest in Internet numbering issues is welcome to observe, participate and contribute to the WG. To post a message to the list, send an email to address-policy-wg@ripe.net. Please note that only subscribers can post messages.

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.