Archive for December, 2010

ARIN starts data transfer

Thursday, December 23rd, 2010

This is second of a number of updates regarding the transition of the IN-ADDR.ARPA zone.

As of today, the 23rd of December 2010, ARIN commenced a process of transferring the zone data  and zone configuration data to ICANN via a secure channel. This upload occurs daily and paves the way for the next steps in the transition process.

In the coming weeks, this data will be validated, and imported into ICANN systems, republished on a non-authoritative nameserver, and tested for consistency. Details of the available nameserver will be published soon.

Who Serves IN-ADDR.ARPA?

Friday, December 10th, 2010

At present, the authoritative set of name servers which serve IN-ADDR.ARPA are:

(in no particular order)


This represents 12 of the 13 root-servers.


Friday, December 10th, 2010

The IN-ADDR.ARPA zone is a critical service for Internet operations as it provides a guaranteed method to perform host address to host name mapping. The delegations which exist in this zone represent the ‘/8’ IPv4 delegations to the registrants of the corresponding IANA function allocations to legacy registrants and Regional Internet Registries. Since 1997 ARIN has performed technical management function of zone editor and zone generator as inherited from InterNIC.

The IN-ADDR.ARPA zone is a sub domain of the ARPA top-level domain. ARPA sub domain management principles, management guidelines and operational requirements are described in RFC 3172.

Transition Commences

Friday, December 10th, 2010

On the 29th November 2010 the transition of the technical management of the IN-ADDR.ARPA DNS zone officially commenced with the exchange of coordination staff details between ARIN and ICANN.

The transition effort, which brings together number of talented professionals from both ARIN and ICANN, will take approximately 11 weeks to complete. The target, at this stage, is to complete the transition on the 14th and 15th of February 2011 resulting in the ability for ICANN to DNSSEC Sign IN-ADDR.ARPA.

The 11 week process to effect this transition consists of a number of stages where significant emphasis is placed on ensuring stable and consistent action that involves multiple testing regimes and sign-off points such that the greater Internet community can be assured that all possible care is being taken.

As of writing this post, the format in which the IN-ADDR.ARPA zone and the operational configuration details will be transferred to ICANN were being confirmed along with the exchange of authorisation credentials necessary to retrieve this data.

More information will be posted in due course.