-------------------------------------------------------------------
APNIC Document identity
Title: APNIC Reverse DNS Delegation Form
Short title: reverse-dns
Document ref: APNIC-077
Version: 003
Date of original publication: February 2000
Date of this version: 31 July 2002
Review scheduled: n/a
Obsoletes: APNIC-064
Status: Obsolete
Comments: Version 004 replaces this form.
--------------------------------------------------------------------
APNIC Reverse DNS Delegation Form
This form is used to provide information to APNIC that will enable the
sub-delegation of in-addr.arpa and ip6.arpa domains. In-addr.arpa and
ip6.arpa domains allow for the mapping of IP addresses into domain names.
YOU MUST SET UP YOUR NAME SERVER TO ACCEPT THE DELEGATION PRIOR TO THE
SUBMISSION OF THIS FORM.
Please see the comments at the bottom of this form regarding how to
complete this application. Note that this form is parsed by machine
and modification of lines starting with #[ or the field names will
likely result in errors being returned to you and your request
not being processed.
The methods for submitting a reverse DNS delegation request are (from
most preferred to least preferred):
1. Complete and submit the web-based form at:
http://www.apnic.net/db/domain.html
2. Complete this text form and submit it via email to:
auto-dbm@apnic.net
3. Submit a request in typewritten English via fax to:
+61-7-3858-3199
(please note, APNIC discourages submissions by fax)
4. Submit a request in typewritten English via postal mail to:
APNIC Pty Ltd
PO Box 2131
Milton QLD 4064
Australia
(APNIC recommends that postal submissions be used only as a last resort)
If you have any questions regarding this form, you may contact us via
email at dns-admin@apnic.net (preferred), fax at the above number, postal
mail at the above address, or via telephone at +61-7-3858-3100 between the
hours of 9:00 AM and 5:00 PM Australian Eastern Standard Time (UTC+10).
Note that we do not accept reverse DNS delegation requests via telephone.
Please allow up to one week for processing electronic mail requests
and up to one month for other forms of submission.
NOTE: IT IS NOT NECESSARY TO INCLUDE THIS HEADER NOR THE INSTRUCTIONS
AT THE BOTTOM OF THIS FORM WITH YOUR APPLICATION.
- - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - -
#[DOMAIN TEMPLATE V4.0]#
domain: [mandatory] [single] [primary/look-up key]
descr: [mandatory] [multiple] [ ]
country: [optional] [single] [ ]
admin-c: [mandatory] [multiple] [inverse key]
tech-c: [mandatory] [multiple] [inverse key]
zone-c: [mandatory] [multiple] [inverse key]
nserver: [mandatory] [multiple] [inverse key]
remarks: [optional] [multiple] [ ]
notify: [optional] [multiple] [inverse key]
mnt-by: [mandatory] [multiple] [inverse key]
mnt-lower: [mandatory] [multiple] [ ]
changed: [mandatory] [multiple] [ ]
source: [mandatory] [single] [ ]
#[TEMPLATES-END]#
- - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - -
1. Instructions for obtaining Reverse DNS Delegation
-----------------------------------------------------
Please submit this form after providing appropriate values for all
mandatory fields. After completing the form, submit it to
auto-dbm@apnic.net where it will be processed to determine whether the
delegation can proceed.
For the delegation to proceed, all listed DNS servers must be visible to
the Internet and *MUST BE CONFIGURED*. In addition, the network for which
you are attempting to gain delegation *MUST BE REGISTERED* in the
APNIC Registration database. Failure to observe these requirements
will result in your application being rejected.
As always, if you have any questions or comments regarding this form,
please contact dns-admin@apnic.net at your convenience.
2. Details for completing the DOMAIN Template
----------------------------------------------
domain:
Please provide either the in-addr.arpa or ip6.arpa domain you wish to
have delegated. If you wish to have multiple sub-domains delegated
then you will need to submit multiple copies of the form as
appropiate. This can also be done in one email message.
Example:
1.202.in-addr.arpa or
0.0.0.2.0.1.0.0.2.ip6.arpa
Please note that ip6.int is now deprecated. Holders of IPv6 address
space with existing ip6.int domain objects are requested to create
ip6.arpa reverse domains and to maintain both ip6.arpa and ip6.int
objects. As client software becomes more stable and performs lookups
in ip6.arpa before ip6.int, it will no longer be necessary to
maintain ip6.int domain objects.
descr:
A short informative description of the intended use of the relevant
IP range.
Example:
Reverse DNS for <My Organisation>.
country:
Name of the country of the admin-c.
2 letter uppercase ISO 3166 code.
A listing of ISO 3166 codes can be found from the ISO 3166
Maintenance Agency, at http://www.din.de/gremien/nas/nabd/iso3166ma/
admin-c:
An on-site contact person.
tech-c:
A technical contact person.
zone-c:
NIC-handle of the person with authority over a zone.
nserver:
List of nameservers for a domain object; a minimum
of two is mandatory.Please use fully qualified domain name
(FQDN) of the nameserver and not the IP address.
remarks:
General remarks. Can include an URL or RFC822
address (if preceeded by "mailto:").
notify:
The e-mail address to which notifications of changes to
an object should be sent.
mnt-by:
The identifier of an APNIC registered mntner object used for
authorization and authentication.
mnt-lower:
The identifier of an APNIC registered mntner object used for
hierarchical authorization and authentication.
changed:
Who previously changed this object and when this change was made.
E-mail address of person updating the object.
DATE in YYYYMMDD or YYMMDD format.
source:
Identifier of the database containing authoritative data for
this object. Use APNIC for objects in the APNIC Database.
Uppercase Text.
3. Supporting Notes
-------------------
3.1 What is an in-addr.arpa/ip6.arpa domain
The Internet uses special domains to support address to name mapping,
referred to as inverse addressing (in-addr.arpa and ip6.arpa) or
reverse nameserving. Inverse addressing is necessary when you have an
IP address and want to obtain the name associated with that address.
Many servers in use on the Internet today make use of inverse
addressing to obtain the domain name of hosts connecting to those
servers. As these applications use this information for log files, in
many cases they will refuse service unless the inverse nameserver
provides an appropriate name.
in-addr.arpa and ip6.arpa domains are represented using the network
number in reverse. For example, the in-addr.arpa domain for network
123.45.67.0 is represented in the DNS as 67.45.123.in-addr.arpa. The
ip6.arpa domain for network 2001:0200::/35 is represented in the DNS
as 0.0.2.0.1.0.0.2.ip6.arpa.
Please note that ip6.int is now deprecated. Holders of IPv6 address
space with existing ip6.int domain objects are requested to create
ip6.arpa reverse domains and to maintain both ip6.arpa and ip6.int
objects. As client software becomes more stable and performs lookups
in ip6.arpa before ip6.int, it will no longer be necessary to
maintain ip6.int domain objects.
3.2 Use of Classless Networks
The DNS, in particular the in-addr.arpa tree, is one of the last
bastions of classful addressing with delegations performed on byte
boundaries. For example, the delegations will occur for 202.in-addr.arpa
for networks in the class A equivalent of 202.0.0.0 - 202.255.255.255,
12.202.in-addr.arpa for the networks in the class B equivalent of
202.12.0.0 - 202.12.255.255 and for the class C network, 202.12.28.0.
This makes the delegation of classless addresses that happen
to fall outside a classful boundary somewhat awkward. In general,
one must delegate each classful component of a classless network,
For example in the case of a /17, all class C networks that make up that /17
will need to be delegated. RFC 2317 describes techniques useful for
classless delegation.
4. References
-------------
For those who need help in configuring the DNS, the following
publications will provide useful advice:
DNS and Bind, Paul Albitz & Cricket Liu, O'Reilly & Associates,
ISBN 1-56592-010-4
TCP/IP Network Administration, Craig Hunt, O'Reilly & Associates,
ISBN 0-937175-82-X
P. Vixie, et al, "BIND Source Distribution, version 8.2.2", 5/11/1998,
URL: ftp://ftp.isc.org/isc/bind/src/cur/bind-8/bind-8.2.2-src.tar.gz
RFC 1886 S. Thomson, C. Huitema, "DNS Extensions to support IP version 6",
1/12/1995, URL: http://ftp.apnic.net/ietf/rfc/rfc1000/rfc1886.txt
RFC 1912 D. Barr, "Common DNS Operational and Configuration Errors",
2/1/1996, URL: http://ftp.apnic.net/ietf/rfc/rfc1000/rfc1912.txt
RFC 2317 H. Eidnes, G. de Groot, P. Vixie, "Classless IN-ADDR.ARPA
delegation". 3/1/1998,
URL: http://ftp.apnic.net/ietf/rfc/rfc2000/rfc2317.txt
APNIC documents (not commercially available publications) are
available from the APNIC document store in the directories mentioned
in the URLs. The APNIC document store can be accessed via anonymous
FTP from host archive.apnic.net
Using your ftp application (usually called simply 'ftp'), connect to
host archive.apnic.net using your email address as the password.
For RFCs, use the "change directory" command (typically 'cd') to
'/ietf/rfc'. For APNIC documents, 'cd' to '/apnic/docs'. You
may then use the "get" command (typically 'get') to retrieve the
specific file.
You may also access the APNIC document store by directing your web
browser to http://ftp.apnic.net.
=======================END===========================
(c) APNIC Pty Ltd 2000