Reverse DNS delegations using ip6.arpa and ip6.int

Please note: this message has now been obsoleted. From May 2005, ipv6.int is now deprecated at APNIC.

Please note: this message has now been obsoleted. From May 2005, ipv6.int is now deprecated at APNIC.

Background

In conformance with RFC 3152 , IPv6 reverse DNS delegations are now being made under the ip6.arpa domain rather than ip6.int.

ip6.arpa is available at APNIC

Holders of IPv6 address space must begin creating reverse domain objects using ip6.arpa.

Software is available to support the transition from ip6.int to ip6.arpa lookups.

Eventually, ip6.int will be phased out, so it is important to make the transition to ip6.arpa as soon as possible.

Existing ip6.int reverse domain objects

Existing ip6.int reverse domain objects remain valid.

APNIC has created equivalent ip6.arpa reverse domain objects for all ip6.int reverse domain objects currently in the APNIC Whois Database. These new ip6.arpa reverse domain objects are maintained by the same maintainer as the original ip6.int reverse domain object.

However, these ip6.arpa delegations will not be visible on global nameservers until the organization responsible for the reverse DNS delegation has created the appropriate zone files and modified the reverse domain object accordingly. To do this, please do the following:

  1. Create the reverse zone file
  2. Update the "nserver" attribute of your reverse domain object

The ip6.arpa reverse delegation will then be propogated to the APNIC nameserver, and then to global nameservers.

Maintaining ip6.int and ip6.arpa reverse domain objects

Maintenance of delegations within ip6.int is still supported by APNIC, but is optional. However, please note that ip6.int and ip6.arpa reverse domains are independent objects and need to be updated separately.

When client software is stable and performs lookups in ip6.arpa zones before ip6.int zones, it will no longer be neccessary to maintain ip6.int domain objects.

More information

Contact:

Phone: