Maintainer template

The maintainer template is used to create a new maintainer object that can be used to protect other objects in the APNIC Whois Database.

Attributes in maintainer template:

mntner
descr
country
admin-c
tech-c
upd-to
auth
remarks

Maintainer name (mntner)

The name of the maintainer (mntner) should be a short, but meaningful name for this maintainer.

If you are creating a maintainer to protect resource registrations, please use the format:

Organisation maintainer

<maint>-<iso-3166-code>-<organisation>

Example:

MAINT-WF-SPARKYNET

Personal maintainer

If you are creating a maintainer that will be applied to a person object, please use the format:

<maint>-<iso-3166-code>-<person>

Note: do not use a personal maintainer to protect any object other than a person object. To protect resource registration details, use an organisation maintainer.

Example:

MAINT-WF-ZANE-ULRICH

Top

Description of maintainer (descr)

The description of maintainer (descr) should be a brief description of the maintainer. This should include enough detail to distinguish it from other maintainer objects.

Please limit the descr attribute to no more than five lines.

Example:

descr: Maintainer for Sparkynet
descr: Webhosting, dialup, leased line
descr: Wallis and Futuna Islands

Top

ISO 3166 code of organisation or person responsible for maintainer (country)

The country attribute should contain the most appropriate two-letter ISO-3166 code for the organisation or person responsible for the maintainer.

In cases where the more than one country or economy may be appropriate, please use the ISO 3166 code of the country or economy where the maintainer object's administrative contact (admin-c) is located..

Example:

country: WF

Top

Administrative contacts (admin-c)

The please select the help that suits you needs:

Resource registration maintainer
Person object maintainer
Person object already created
Person object being created using this form

Resource registration maintainer

If you are creating a maintainer to protect resource registrations, please specify the NIC-handle of a person who is physically located at the site of the network, subject to the following exceptions:

For residential networks or users, the IR's technical contact may be registered as admin-c.
For networks in exceptional circumstances that make it impractical to maintain an on-site administrative contact, an off-site person may be registered as the admin-c.

Back to admin-c

Person object maintainer

If you are creating a maintainer to protect a person object, you can refer to that person object as the admin-c.

Back to admin-c

Person object already created

If you do have a person object already created in the database, please enter the contact in the NIC- handle (person object) format.

Example:

admin-c: KX9-AP

Back to admin-c

Person object being created using this form

If you do not yet have a person object created, please complete the person object template included in the APNIC Maintainer and Person Request Form and use the NIC-handle AUTO-1 already completed in the maintainer template's admin-c attribute. If you wish to refer to additional person objects also being created in this form, please complete additional person object templates and increment the AUTO NIC-handle.

Example:

admin-c: AUTO-1
admin-c: AUTO-2

Back to admin-c | Top

Technical contacts (tech-c)

The please select the help that suits you needs:

Resource registration maintainer
Person object maintainer
Person object already created
Person object being created using this form

Resource registration maintainer

If you are creating a maintainer to protect resource registrations, please specify the NIC-handle of a person who is responsible for the day-to-day operation of the network, but does not need to be physically located at the site of the network. You may specify more than one tech-c for the network.

Back to tech-c

Person object maintainer

If you are creating a maintainer to protect a person object, you can refer to that person object as the tech-c.

Back to tech-c

Person object already created

If you do have a person object already created in the database, please enter the contact in the NIC- handle (person object) format.

Example:

tech-c: KX9-AP

Back to tech-c

Person object being created using this form

If you do not yet have a person object created, please complete the person object template included in the APNIC Maintainer and Person Request Form and use the NIC-handle AUTO-1 already completed in the maintainer template's tech-c attribute. If you wish to refer to additional person objects also being created in this form, please complete additional person object templates and increment the AUTO NIC-handle.

Example:

tech-c: AUTO-1
tech-c: AUTO-2

Back to tech-c | Top

Notification of updates (upd-to)

The upd-to attribute contains an e-mail address to which notifications of changes to the maintainer should be sent. Use this attribute to assist in object maintenance by listing email addresses of people who should be notified of any changes or attempted changes to this object.

Note: not use the upd-to attribute as a network contact address.

Example:

upd-to: noc@example.com

Top

Authorisation method (auth)

The authorisation method (auth) attribute specifies the scheme used to authenticate update requests for objects protected by this maintainer.

Authentication options available are:

CRYPT-PW
PGP-KEY
MD5

For information on how to use these authentication options, see Authentication options for maintainer objects.

Example:

auth: CRYPT-PW apL5ifB7

Top

Remarks (remarks)

The remarks attribute can be used for any remarks about the maintainer that cannot be expressed in any of the other attributes. Remarks should be only be included if they provides extra information to users of the database.

You may use multiple lines, but please keep remarks to a minimum.

Example:

remarks: Send spam and abuse reports to abuse@example.com

Top | Guide to the APNIC Maintainer and Person Object Request Form (text version)