The object template includes information on how to complete the attribute values.
Status Instance Search Status role: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] country: [mandatory] [single] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [mandatory] [multiple] [lookup key] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse 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] last-modified: [generated] [single] [ ] source: [mandatory] [single] [ ]
role: D EXAMPLENETADMIN 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 admin-c: ABC123-AP tech-c: ABC123-AP nic-hdl: DE345-AP remarks: http://www.examplenet.com.au notify: firstname.lastname@example.org mnt-by: MAINT-EXAMPLENET-AP last-modified: 2018-08-30T07:50:19Z source: APNIC 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 last-modified: 2018-08-30T07:50:19Z source: APNIC
Attribute must be included in the object. Failure to do so will result in errors.
|role||The full name of an administrative, technical or zone contact person referenced in another object.
EXAMPLE APNIC DBM
|address||Full postal address for the role account.
EXAMPLE address: 2 Pandora St Boxville address: Wallis and Futuna Islands
|phone||Telephone number for the role function.
+ <international code> <area code> <phone #> + <international code> <area code> <phone #> ext.
EXAMPLE phone: +681 368 0844 ext. 32
|The email address for the role account.
|admin-c||The NIC-handle of an on-site contact ‘person’ object. As more than one person often fulfills a role function, there may be more than one admin-c listed.
|tech-c||The NIC-handle of a technical contact ‘person’ or role object. As more than one person often fulfills a role function, there may be more than one tech-c listed.
|nic-hdl||The NIC-handle of the ‘role‘ or person object.
The APNIC NIC-handle takes the format:
NIC-handle (Network Information Centre handle):
When creating a person/role object, set the value of the attribute to either:
|mnt-by||Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.
EXAMPLE mnt-by: MAINT-SPARKY-WF
|last-modified||It is a time stamp that is generated by the system to reflect when the object was last modified.
|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 role function.
+ <international code> <area code> <fax #>
EXAMPLE fax-no: +681 367 1797
|trouble||Information on who to contact when there are problems.
Can be used to include details on where to send abuse complaints.
|remarks||Information about the object that cannot be stated in other attributes. Remarks can include a URL or RFC 822 address (if preceded by mailto:)
|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.
Using role objects
Role objects have three main advantages:
- While certain roles within an organization may remain stable, the people performing those roles may change.
Using a role object means that when people in the organization change, only the role object needs to be updated instead of all associated ‘inetnum’ and ‘aut-num’ objects.
- You can specify a generic email address for the role object.
For example, email@example.com, so network queries are sent to a mailbox that may be accessed by many people, instead of to an individual staff member’s mail box.
- Role objects have a ‘trouble’ field, which describe an additional email box you use for spam and network abuse reports.
This can take the burden off a single person and allow abuse reports to be handled by your abuse team.