Domain template

Attributes in reverse domain object:

domain
descr
country
admin-c
tech-c
zone-c
nserver
remarks
notify
mnt-by
mnt-lower
changed
source

Reverse DNS zone (domain)

Please provide either the in-addr.arpa or ip6.arpa domain you wish to have delegated in the domain field. If you wish to have multiple sub-domains delegated then you will need to submit multiple copies of the template as appropriate (this can be done in a single email).

Example:

domain:    1.202.in-addr.arpa              
domain:    0.0.0.2.0.1.0.0.2.ip6.arpa

Top

Description of domain object (descr)

You must include a short informative description of the intended use of the relevant IP range in the descry field.

Example:

descr:    Reverse DNS for SPARKNET.COM.WF

Top

ISO 3166 code (country)

The country field should contain the two-letter ISO 3166 code that is appropriate for your organisation.

In cases where the more than one country or economy may be appropriate, please use the country or economy where the administrative contact is located.

Top

Administrative contacts (admin-c)

An administrative contact (admin-c) must be someone who is physically located at the site of the network. You may specify more than one admin-c for the network.

You should enter these contacts in the NIC handle (person object) format.

Example:

KX9-AP

If these contacts do not yet have valid NIC handles, please create them before submitting the reverse DNS form.

Top

Technical contacts (tech-c)

A technical contact (tech-c) must be a person 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.

You should enter these contacts in the NIC-handle (person object) format.

Example:

KX9-AP

If these contacts do not yet have valid NIC-handles, please create them before submitting the reverse DNS form.

Top

Zone contact (zone-c)

A zone contact must be a person with authority over the zone. You may specify more than one zone-c for the network.

You should enter these contacts in the NIC-handle (person object) format.

Example:

KX9-AP

If these contacts do not yet have valid NIC handles, please create them before submitting the reverse DNS form.

Top

Nameservers (nserver)

A list of primary and secondary nameservers for a domain object. A minimum of two is mandatory. Each nameserver should be on a separate line and and must take the following format:

Fully qualified domain name(s) with or without trailing "."

Please note: APNIC does not use glue records. Therefore, please ensure that the nameserver is outside the in-addr.arpa or ip6.arpa zone.

Valid nameserver in domain object:

domain:  28.12.202.in-addr.arpa
nserver: ws1.apnic.net

Invalid nameserver in domain object:

Example:

domain:  28.12.202.in-addr.arpa
nserver: a.ws.28.12.202.in-addr.arpa

Top

remarks

General remarks related to the domain object. Remarks can include a URL or an email address.

Example:

remarks: http://www.sparkynet.com.wf

Top

Who to notify of changes to object (notify)

When changes are made to the role object, the email address specified in this field is sent notification of the changes.

Please use the address format specified in RFC-822.

Example:

notify:      hostmaster@sparkynet.com.wf

Top

Maintainer authorised to make changes to object (mnt-by)

The identifier of a registered mntner object used for authorisation and authentication.

A maintainer object is a database object used to authorise updates to the APNIC database. If your database details are protected by a maintainer object, then only people with access to the security information of that maintainer object will be able to change details.

APNIC strongly recommends that you do create a maintainer object.

Example:

mnt-by:      MAINT-SPARKY-WF

Top

Details of when the object was last changed (changed)

The identifier of an APNIC registered maintainer object used to authorise and authenticate the creation of reverse domain objects more specific than the current reverse domain object.

Top

Lower maintainer authorised to make changes (mnt-lower)

The changed field displays a list of who previously changed this object and when these changes were made. The field displays the email address of the person updating the object. This is followed by the date.

Please use the address format specified in RFC-822 and provide the date format using one of the following two formats: YYYYMMDD or YYMMDD.

Example:

changed:     hostmaster@sparkynet.com.wf 20010921

Top

Authoritative database source of the object (source)

The source field identifies the database containing authoritative data for this object. For objects registered in the APNIC Whois Database, please enter 'APNIC'. The entry must use uppercase text only.

Example:

source: APNIC

Top | Guide to the APNIC reverse domain request form