Archive for February, 2011

Transition Process

Wednesday, February 16th, 2011

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

As of 11.15am 16th February UTC-8, today, the action items listed in the Process and timeline for IN-ADDR.ARPA transition were successfully completed.

This transition at this stage results in:

  • ICANN as the technical manager of IN-ADDR.ARPA.
  • IN-ADDR.ARPA being served by the 6 nameservers described in RFC 5855 and operated by the five RIRs and ICANN.
  • IN-ADDR.ARPA DNSSEC-signed by the same systems that signs many ICANN-operated zones including IP6.ARPA, IP6-SERVERS.ARPA, IN-ADDR-SERVERS.ARPA, IANA.ORG, and ICANN.ORG.
  • A conservative plan in place to remove IN-ADDR.ARPA from the 12 root servers that currently serve it.

On 14 March 2011 a request will be sent to the IANA to add DS records to the IN-ADDR.ARPA delegation. It is expected that this change will take several days to complete due to the required authorisations.

The delay between transition and adding DS records to the root zone facilitates a simple rollback procedure in the (unlikely) event that harmful effects of DNSSEC in the IN-ADDR.ARPA zone are observed.

Final updates regarding the root servers and DS submission will be posted here as necessary.

Process and timeline for IN-ADDR.ARPA transition

Wednesday, February 9th, 2011

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

ARIN and ICANN have agreed to the following process details for the transition of the IN-ADDR.ARPA DNS zone.

On 16th February at 9am UTC-8:

  • ICANN takes last agreed update from ARIN and publishes the zone via the namservers. The agreed update from ARIN will be the generated zone data for the time stamp “201102160445”.
  • ICANN will disable any further imports from ARIN.
  • Both ARIN and ICANN will confirm zone contents (delegated NS) match between servers and the root servers and signoff by 9.30am UTC-8
  • ICANN to advise VerSign (root server hidden master operator) to pull IN-ADDR.ARPA from ICANN at 10.00am UTC-8
  • ICANN will advise IANA to continue processing of the IN-ADDR.ARPA delegation change
  • ICANN will update //
  • ICANN and ARIN to publish a statement of transition
  • ICANN to publish/update appropriate whois records for * delegations on
  • ICANN to provide public AXFR to  IN-ADDR.ARPA on
  • ICANN to publish IN-ADDR.ARPA zone on the site

During this transition a 48 hour update embargo will be placed on the IN-ADDR.ARPA zone. This will run from0000hrs 16th February UTC-8 to 2400hrs 17th February UTC-8.