Transfer of AUNIC network records

During May 2001, all network records within the AUNIC database were moved to the APNIC database. These records were removed from AUNIC on July 1.

The IP range affected was: 203.0.0.0 to 203.63.255.255

After this transfer was completed, the AUNIC database was no longer authoritative for IP addresses within that range.

Policy changes that affected former AUNIC ranges

Recovery of unused historical IP addresses	A significant amount of historical address space registered in the APNIC Whois Database was not announced to the global routing table. To recover these globally unrouted resources and place them back in the free pool for reallocation to other networks, APNIC contacted the networks responsible for historical address space in the APNIC region that had not been globally routed since 1 January 1998. Refer to Section 5 of the Policies for historical Internet resources in the APNIC Whois Database For more information, see: Guide to the recovery of unused address space.
Transferring IP addresses to another organization	To transfer historical Internic or AUNIC resources to a current APNIC account holder, please see: Section 4 of the Policies for historical Internet resources in the APNIC Whois Database For more information, see: Guide to the recovery of unused address space.
Updating information in the APNIC Whois Database	To ensure the integrity of information in the APNIC Whois Database, APNIC will not update historical information in the APNIC Whois Database until the resource holder can prove their organization's right to the resources and has a formal agreement with APNIC as a member or non-member account holder. Refer to Section 6 Policies for historical Internet resources in the APNIC Whois Database For more information, see: Guide to the recovery of unused address space
Change to person objects	As part of this transfer, all person objects referenced by the above network objects were copied to the APNIC database. Please note the objects in the range above were not deleted from the AUNIC database. Where possible, the same initials and numbers were used for the nic-handle, substituting '-AP' for '-AU'. Where doing so conflicted with an existing APNIC person object, the first available nic-handle was used. For example, for the AUNIC nic-handle 'XY123-AU', two things could happen: 'XY123-AP' does not already exist in the APNIC database and is transferred as is If 'XY123-AP' already exists in the APNIC database, the next available nic-handle is chosen - 'XY124-AP' A letter has been sent to the email addresses of all person objects affected by this change, together with information on how to use the APNIC database (for example, user authentication for changes, how to manage reverse delegations, and so forth).

APNIC membership

As of 3 December 2001, APNIC now has a new membership category that caters for networks responsible for the smaller address blocks allocated within the former AUNIC range. Networks with up to and including a /22 are now eligible to become Very Small Members for an annual fee.

See what APNIC Membership can offer your organization.

Need help?

Before you contact APNIC, please read all the documents linked from this page. If you still have concerns about the transfer of your records from the AUNIC database to APNIC, please contact the APNIC helpdesk with details of your specific concerns.

Migration Timeline

2001
1, May	Network updates handled by auDA for AUNIC are suspended. These will be forwarded to APNIC when the AUNIC to APNIC migration (of 203/10) is completed.
1, May	Migration of the AUNIC networks Database to APNIC begins.
14, May	APNIC begins generating most of the historical AUNIC in-addr.arpa zone files. Updates to delegations within 203/10 become live at 10am (UTC+1000) on weekdays.
29, May	Whois queries directed to whois.apnic.net rather than whois.aunic.net.
31, May	APNIC notifies registrants in the former AUNIC space of database changes.