APNIC Home APNIC Home

You're here:  Home » Database services » AUNIC to APNIC

Modifying objects formerly in the AUNIC database

Contents

Password protection for former AUNIC records

As part of the AUNIC to APNIC migration of network records, all objects imported from the AUNIC database are now protected by a maintainer. A maintainer is used to stop unauthorised updates. To update any AUNIC objects in the APNIC Whois Database, you need to provide the password associated with the maintainer of the object. The AUNIC term for password was 'registry key'. Please note that the original registry key cannot be used to update records in the APNIC Whois Database.

If you do not know the password of the maintainer which protects your objects in the APNIC Whois Database, please contact APNIC and request a new password. More information is included below.

However, before obtaining your password, it is important that you understand how the APNIC database works.

Top

Introducing the APNIC database to AUNIC address holders

The APNIC database is based on objects.

Example:

  • network object, called inetnum, describes an IPv4 network range
  • person object, called nic-handle (nic-hdl), describes a person
  • maintainer object, called mntner, contains details of who is authorised to make changes to related APNIC database objects.

An object can refer to other objects. For example, the inetnum object refers to nic-handle objects within the admin-c and tech-c fields and to a mntner object in the mnt-by field.

Top

Maintainer objects

The APNIC database uses the mntner object to verify that a requested update is being sent from a person with legitimate access to the database records.

The authorisation information in the mntner object is specified in the auth field.

Example:

auth: CRYPT-PW goqtgy2Krmq5w

The password (encrypted in the example above) must be supplied before the protected object can be updated.

Top

Maintainer objects for records imported from the AUNIC database

Each nic-handle imported from the AUNIC database is protected by its own maintainer object. Each network object is protected by the maintainer objects of both the admin-c and tech-c.

Top

Obtaining a password to update your records

To obtain a new password, send an email to helpdesk@apnic.net. Include copies of the address block (inetnum) and person objects you wish to change. APNIC Hostmasters will then reply to you with instructions on how to obtain the password.

Top

Changing objects in the APNIC database via the Web

You can make changes to your objects via the following forms:

Top

Changing objects in the APNIC database via email

In following the above email instructions, please note that an additional line specifies the password. This line is located immediately after the source line for each object:

Example:

[rest-of-object]
source:   APNIC
password: unencrypted password

Top

AUNIC and APNIC databases are not mirrored

As of 1 June 2001, the records in the APNIC database have become the active records of AUNIC allocations. The AUNIC database will still contain a legacy copy of IP address records until 1 July 2001. However, the AUNIC database is not a mirrored version of APNIC's records and will not be updated to include changes made to objects in the APNIC database.

Therefore, when you amend objects imported from AUNIC to the APNIC database, your changes will only appear in the records of the APNIC database. They will not appear in the AUNIC database.

If you experience difficulties, please contact helpdesk@apnic.net.

Top  |  AUNIC to APNIC


Last modified Wednesday, 30-Nov-2005 14:50:31 EST | © 2001 APNIC Pty. Ltd. Contact us