The object template includes information on how to complete the attribute values.
Status Instance Search Status mntner: [mandatory] [single] [primary/lookup key] descr: [mandatory] [multiple] [ ] country: [optional] [single] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [optional] [multiple] [inverse key] upd-to: [mandatory] [multiple] [inverse key] mnt-nfy: [optional] [multiple] [inverse key] auth: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] abuse-mailbox: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] referral-by: [mandatory] [single] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]
mntner: MAINT-NZ-EXAMPLENET descr: maintainer for Example net Pty Ltd country: NZ admin-c: DE345-AP tech-c: DE345-AP upd-to: firstname.lastname@example.org mnt-nfy: email@example.com auth: PGPKEY-83F2A90E notify: firstname.lastname@example.org mnt-by: MAINT-EXAMPLENET-AP referral-by: APNIC-HM changed: email@example.com 20101231 source: APNIC 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: firstname.lastname@example.org admin-c: ABC123-AP tech-c: ABC123-AP nic-hdl: DE345-AP remarks: http://www.examplenet.com.au notify: email@example.com mnt-by: MAINT-EXAMPLENET-AP changed: firstname.lastname@example.org 20101231 source: APNIC
Attribute must be included in the object. Failure to do so will result in errors.
|mntner||The unique name of a mntner object. APNIC recommends the following formats: Maintainer for resource registrations:
<maint>-<iso3166-code>-<organization> EXAMPLE MAINT-WF-SPARKYNET
Maintainer for a ‘person’ object:
<maint>-<iso3166-code>-<person> EXAMPLE MAINT-WF-ZANE-ULRICH
|descr||A short description of the mntner object and the name of the organization associated with it.|
|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.
|upd-to||The email address to be notified when attempts to update objects protected by the mntner are rejected due to a lack of authentication.|
|auth||Scheme used to authenticate update requests. Authentication options available are:
CRYPT-PW PGP-KEY MD5 EXAMPLE: auth: PGP-499E1F0A
For information on how to use these authentication options see:
|mnt-by||Lists a registered mntner used to authorize and authenticate changes to this object.
|referral-by||The maintainer that created this mntner object. Once the mntner object has been created, this attribute cannot be altered. All mntner objects are manually created by APNIC hostmasters, so this attribute will contain:
|changed||The email address of who last updated the database object and the date it occurred.
changed: email@example.com 20010921
IMPORTANT! This is NOT to be used as a contact address.
|source||The name of the database from which the data was obtained.
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
|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.
|mnt-nfy||The email address to be notified when an object protected by a mntner is successfully updated.|
|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.