Register Reverse Delegations with APNIC
Important
Ensure that the zone has been loaded on your nameserver and associated secondaries before filling out this form. The diagnostic script uses both UDP and TCP to verify the nameservers (may cause timeouts if you block TCP port 53).
In the case of /16 level delegations (i.e., X.X.in-addr.arpa rather than /24 delegations, X.X.X.in-addr.arpa), APNIC can secondary the zone from your name servers in order to increase the visibility of your reverse delegations if required. Contact dns-admin@apnic.net for further information.
View, modify, or delete an existing domain object
To view, modify, or delete an existing domain object, please enter the domain of interest below, for example: 123.153.203.in-addr.arpa
AUNIC reverse delegation
From 1 June 2001, AUNIC delegations (203.3.3.0 to 203.63.255.255) also used this form.
For more information on the migration of network records from the AUNIC to APNIC database, please see AUNIC to APNIC Migration.
If you need help registering a reverse delegation for space previously registered by AUNIC, please contact helpdesk@apnic.net.
Detailed setup guides exist for setting up your IN-ADDR.ARPA (IPv4) and the IP6.arpa (IPv6) domains. These guides describe how to create appropriate in-addr.arpa or ip6.arpa zone files and how to get them running on your nameservers. These steps must be completed before you use the forms available here in future.
Create a new domain object
This feature will be available in future.
You will need to have the appropriate in-addr.arpa or ip6.int zone available on your nameservers first before continuing with this form. See the setup guides above. APNIC will only perform reverse delegations on the '.' boundaries. If you have less than 255 IP addresses, please contact your upstream provider.