The object template includes information on how to complete the attribute values.
Status Instance Search Status person: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] country: [mandatory] [single] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [mandatory] [multiple] [lookup key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] abuse-mailbox: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]
person: Albert Brooke Crichton address: 123 Example st. address: 20097 Exampletown country: AU phone: +12 34 567890 000 fax-no: +12 34 567890 010 e-mail: email@example.com nic-hdl: ABC123-AP notify: firstname.lastname@example.org mnt-by: MAINT-EXAMPLENET-AP changed: email@example.com 20101231 source: APNIC
Attribute must be included in the object. Failure to do so will result in errors.
|person||The full name of an administrative, technical or zone contact person referenced in another object.|
|address||Full postal address for the person.|
|phone||Telephone number for the person.|
|The email address for the person.
Need to report abuse and spam? find out how here . . .
|nic-hdl||The NIC-handle of the ‘role‘ or person object.
The APNIC NIC-handle takes the format:
The database will generate a NIC-handle. This newly generated handle is created depending on the initials in the name of the person/role object.
Syntax: For 2 to 4 characters optionally followed by up to 5 digits with the suffix “-AP”.
|mnt-by||Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.
EXAMPLE mnt-by: MAINT-SPARKY-WF
|changed||The email address of who last updated the database object and the date it occurred.
changed: firstname.lastname@example.org 20010921
IMPORTANT! This is NOT to be used as a contact address.
|source||The database where the object is registered.
Attribute may be deleted from the object. To delete an optional attribute you must also remove the attribute from the object template. Failure to do so will result in errors.
|country||Two letter ISO 3166 code of the country or economy where the admin-c is based.
Please use UPPERCASE letters.
EXAMPLE country: WF
|fax-no||The fax number for the person.|
|remarks||General remarks. May include a URL or email address.|
|notify||The email address to which notifications of changes to this object should be sent.
Attribute value is generated by the database.
This object can be created and updated in MyAPNIC.
Instances of attribute allowed
|Attribute must appear only once in the object.|
|Attribute may appear multiple times in the object. For example, you may wish to include more than one admin-c attribute.|
Attribute search status
|Primary keys distinguish an object from all other objects in the database.
To update a primary key, you must delete the entire object and them create a new object with the updated information.
|Attribute can be queried in the database to return the object. Please note, however, that a lookup key does not uniquely identify an object.|
|Attribute can be used when performing an inverse query using the -i flag. For example, the query
-i mntner <MNTNER-NAME>
will return all objects with the specified maintainer in the mnt-by attribute.