Archive for January, 2011

Planned IN-ADDR.ARPA Nameserver Change

Monday, January 31st, 2011

This is a courtesy notification of an upcoming change to the
nameserver set for the IN-ADDR.ARPA zone.

There is no expected impact on the functional operation of the DNS
due to this change.

There are no actions required by DNS server operators or end users.

DETAIL

The IN-ADDR.ARPA zone is used to provide reverse mapping (number
to name) for IPv4. The servers which currently provide authoritative
DNS service for the IN-ADDR.ARPA zone are as follows:

A.ROOT-SERVERS.NET
B.ROOT-SERVERS.NET
C.ROOT-SERVERS.NET
D.ROOT-SERVERS.NET
E.ROOT-SERVERS.NET
F.ROOT-SERVERS.NET
G.ROOT-SERVERS.NET
H.ROOT-SERVERS.NET
I.ROOT-SERVERS.NET
K.ROOT-SERVERS.NET
L.ROOT-SERVERS.NET
M.ROOT-SERVERS.NET

On Wednesday 2010-02-16 processing will begin to change the nameserver
set to the following, as described in RFC 5855:

A.IN-ADDR-SERVERS.ARPA (operated by ARIN)
B.IN-ADDR-SERVERS.ARPA (operated by ICANN)
C.IN-ADDR-SERVERS.ARPA (operated by AfriNIC)
D.IN-ADDR-SERVERS.ARPA (operated by LACNIC)
E.IN-ADDR-SERVERS.ARPA (operated by APNIC)
F.IN-ADDR-SERVERS.ARPA (operated by RIPE NCC)

The usual IANA process for a change in the ARPA zone involves a
series of technical checks and the gathering of various authorisations,
and may take several days to complete.

Following this, the IN-ADDR.ARPA zone will be dropped from root
servers in two groups:

1. Week of 2011-02-21 — 2011-02-25

B, C, E, G, I, M

2. Week of 2011-02-28 — 2011-03-11

A, D, F, H, K, L

Individual root server operators will choose a time for the maintenance
within their respective window and follow their usual procedures
to carry out the change.

Posted in IN-ADDR.ARPA | No Comments »

New name servers for IN-ADDR.ARPA

Wednesday, January 12th, 2011

RFC 5855 “Nameservers for IPv4 and IPv6 Reverse Zones” specifies a dedicated and stable set of nameserver names for each of the IN-ADDR.ARPA and IP6.ARPA zones.

Currently IN-ADDR.ARPA is served by a subset of the DNS root servers.

The secure and stable hosting of the IN-ADDR.ARPA and IP6.ARPA zones is critical to the operation of the Internet, since many applications rely upon timely responses to reverse lookups to be able to operate normally.
As a part of the transition process the IN-ADDR.ARPA will be delegated to the following servers operated by ICANN and the 5 RIRs.
  • A.IN-ADDR-SERVERS.ARPA (operated by ARIN)
  • B.IN-ADDR.SERVERS.ARPA (operated by ICANN)
  • C.IN-ADDR.SERVERS.ARPA (operated by AfriNIC)
  • D.IN-ADDR.SERVERS.ARPA (operated by LACNIC)
  • E.IN-ADDR.SERVERS.ARPA (operated by APNIC)
  • F.IN-ADDR.SERVERS.ARPA (operated by RIPE-NCC)

This exercise of delegating a reverse zone to a stable set of names has already been undertaken and completed for IP6.ARPA.

Posted in IN-ADDR.ARPA | No Comments »

IN-ADDR.ARPA republished by ICANN

Wednesday, January 12th, 2011

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

As of today the 12th of January 2011, ICANN is now republishing the zone content provided by ARIN. This version of the IN-ADDR.ARPA zone is available for public query on the following servers.

  • A.IN-ADDR-SERVERS.ARPA
  • B.IN-ADDR-SERVERS.ARPA
  • C.IN-ADDR-SERVERS.ARPA
  • D.IN-ADDR-SERVERS.ARPA
  • E.IN-ADDR-SERVERS.ARPA
  • F.IN-ADDR-SERVERS.ARPA

See RFC5855 for additional details.

The servers under these names are operated by ICANN and the 5 RIRs and will ultimately be made the authoritative nameservers for IN-ADDR.ARPA (in the same way that [A-F].IP6-SERVERS.ARPA is authoritative for IP6.ARPA).

It is worthwhile to note that the zone SOA and zone apex published on [A-F].IN-ADDR-SERVERS.ARPA are different to the current active IN-ADDR.ARPA zone given the new name server set (described by RFC5855). Futher, by virtue of being published through the ICANN DNS systems operated by ICANN DNS Operations, the zone in its republished state is also DNSSEC signed.

Over the next several weeks the ARIN produced zone content will be imported, republished, and audited. During this period any required adjustments will be made before announcing the final transition date.

Posted in Transition Process | No Comments »