Transfer of AUNIC network records
In May 2001, all network records within the AUNIC database were moved to the APNIC database. These records were removed from AUNIC on 1 July 2001.
The IP range affected was: 220.127.116.11 to 18.104.22.168
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.
|Transferring IP addresses to another organization||
To transfer historical Internic or AUNIC resources to a current APNIC account holder, please see:
|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.
|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:
A letter was 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).