------------------------------------------------------------------- APNIC Document identity Title: APNIC IN-ADDR.ARPA Delegation Form Short title: in-addr-request Document ref: APNIC-039 Version: 001 Date of original publication: 1 June 1996 Date of this version: 1 June 1996 Review scheduled: n/a Obsoletes: APNIC-029 Status: Obsolete Comments: Obsoleted by APNIC-049 -------------------------------------------------------------------- APNIC IN-ADDR.ARPA Delegation Form Issued: June 1, 1996 Expires: December 31, 1996* *) This form is valid until superseded by another form. After the date specified, please check the APNIC document store located at ftp://ftp.apnic.net/apnic/docs for a later version of this form. This form is used to provide information to APNIC that will enable the sub-delegation of an in-addr.arpa domain. In-addr.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 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 strange errors being returned to you and your request not being processed. After completing this form, please submit it via email to: domreg@rs.apnic.net or in type written English via fax (discouraged) to: +81-3-5467-7015 or in type written English via postal mail (as a last resort) to: Asia Pacific Network Information Center c/o The United Nations University 53-70, Jingumae 5-Chome, Shibuya-ku, Tokyo 150, Japan If you have any questions regarding this form, you may contact us via email at hostmaster@apnic.net (preferred), fax at the above number, postal mail at the above address or via telephone at +81-3-5467-7014. Note that we do not accept IN-ADDR.ARPA 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 - - - - - - - - - - - - - - - #[IN-ADDR TEMPLATE V3.0]# inetnum: netname: rev-srv: rev-srv: rev-srv: rev-srv: rev-srv: #[TEMPLATES-END]# - - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - - 1.0 Instructions for Obtaining IN-ADDR.ARPA Delegation ------------------------------------------------------ Please submit this form after providing appropriate values for all mandatory fields. After completing the form, submit it to domreg@apnic.net where it will be processed to determine if the delegation can procede. For the delegation to procede, all listed DNS servers visible to the Internet and *MUST BE CONFIGURED*. In addition, the 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 hostmaster@apnic.net at your convenience. 2.0 Details for Filling in the IN-ADDR Template ----------------------------------------------- INETNUM: Please provide the IP network(s) you wish to have in-addr.arpa domain(s) delegated for. If you wish to have multiple networks registered using the same servers, please specify a range of addresses as documented in APNIC-034. Example: inetnum: 202.12.28.0 - 202.12.29.0 NETNAME: Please provide the name associated with this network as assigned by APNIC, do NOT put your NIC handle, the network's domain name, etc. This field is used to cross check the network provided in the INETNUM field to help avoid accidental inappropriate delegation. The APNIC assigned name for network (which may be different than that requested when the network was assigned) can be determined by querying the APNIC whois server with the network number (e.g., whois -h whois.apnic.net and looking for the 'netname' field). Example: netname: APNIC-AP REV-SRV: Please provide the FULLY QUALIFIED DOMAIN NAMES (FQDN) of at least two (and at most five) DNS servers that will provide the in-addr.arpa service. ** DO NOT PUT THE IP ADDRESSES OF THE SERVERS, THE IN-ADDR DOMAIN, ETC. ** Use fully qualified domain names only, e.g., ns.foo.com. You must provide at least TWO (2) DNS servers. If you do not want all five, leave the REV-SRV fields you do not want to fill in blank. 3.0 Supporting Notes -------------------- 1. What is an IN-ADDR.ARPA domain The Internet uses a special domain to support address to name mapping, referred to as inverse-addressing (IN-ADDR) or reverse nameserving. Inverse addressing is necessary when you have an IP address and want to obtain the name assocaiated 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 domains are represented using the network number in reverse. For example, the IN-ADDR domain for network 123.45.67.0 is represented in the DNS and can be looked up as 67.45.123.IN-ADDR.ARPA (note: please do not list your network number in reverse on your template). 2. Use of Classless Networks The DNS, in particular, the in-addr.arpa tree is one of the last bastions of classfull addressing as delegations are 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 obviously make the delegation of classless addresses that happen to fall outside a classfull boundary somewhat awkward. In general, one must delegate each classfull component of a classless network, e.g. in the case of a /17, all class C networks that make up that /17 will need to be delegated. A technique has recently been described in an Internet Draft which allows for the delegation of classless addresses of any prefix length. While not exactly aesthetically pleasing, the technique has been shown to work and does allow organizations to sub-delegate parts of classfull networks. Remembering that Internet Drafts are works in progress, you may obtain the draft from the APNIC archives at the following URL: ftp://archive.apnic.net/ietf/internet-drafts/... draft-degroot-classless-inaddr-01.txt 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 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 in a number of ways: 1. 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. 2. via electronic mail through the APNIC FTP Email gateway You may send mail to 'ftpmail@postoffice.apnic.net' with the body of the message being standard Unix 'ftp' commands. For more help, send an email message to 'ftpmail@postoffice.apnic.net' with a message body consisting of 'help'. Results will be mailed back to you. 3. via WWW to http://rs.apnic.net/archive Using your WWW browser, e.g. Mosaic, Netscape, etc. connect to the URL mentioned above and click on the appropriate subdirectory. Note the APNIC registration service web serve is currently under construction. 4. via gopher to gopher.apnic.net Using your gopher application (usually called 'gopher'), connect to gopher.apnic.net. Move to the "Information about APNIC" branch (choice number 3), then choose the docs branch (choice 2) then choose the appropriate document. If you are looking for IETF documents, choose the "Information About Internet" branch (choice 7), then the "IETF Information" branch (choice 1). Organizations without connectivity wishing to obtain copies of the referenced documents should contact the APNIC or their local registry to arrange postal delivery of one or more of the above documents. Note that some fee may be associated with the delivery of hardcopy versions of documents.