Originally, the Internet began as a research experiment and network known as the ARPANET, which supported the exchange of files and data among government contractors and researchers. As the TCP/IP suite was developed in the early 1980s, the Domain Name System (DNS) emerged as the replacement system to the original ARPANET hosts.txt mechanism. The high-level structure of names used by DNS eventually evolved into five worldwide generic domains (COM, ORG, NET, EDU, and INT), two U.S.-only generic domains (MIL and GOV), and country code domains (for example, US for the United States, AU for Australia, and so on).
The exponential growth of the Internet, due mostly to the connecting of commercial organizations to the Internet over the past couple of years, has had a directly proportional effect on the registration activity of the Registrar.
This explosive growth has placed increased demands on the management of the Net. The Internet could not survive without proper administration of the naming, addressing, routing, and physical trunk backbone management provided by the InterNIC group. This group operates under direction from the National Science Foundation, Network Solutions, and AT&T. The National Science Foundation still provides the primary guidance relative to the Internet. The Internet has moved from a government funded project to a private commercial business funded effort, as a result of this growth.
The first thing any organization must do to get connected to the Internet is to pick an approved Internet Service Provider. The InterNIC is strongly encouraging all interested parties to select an ISP versus trying to establish a direct link into the Internet. The explosive growth on the Internet has placed some very unrealistic demands on the physical infrastructure, which has prompted the InterNIC to start limiting the number of companies directly connected and supported.
You should be very careful in selecting your ISP. Not all ISPs
can handle the traffic you might generate with your particular
Internet connection. Before contacting any ISPs, you should work
through all of the following templates and have a clear picture
of what you require for your particular Internet implementation.
All of the following templates and registration information are
directly from the InterNIC registration Web server. The required
templates are covered in detail under "Selecting Your IP
Addresses" and "Selecting Your Domain Name." The
"Optional Registrations" section covers some items that
you might require for your particular implementation. If you were
going to try to establish your own direct connection to the Internet,
you would need to fill out all these templates and submit them
to the InterNIC electronically at their registration Web server
URL-http://198.41.0.7/rs-internic.html. InterNIC does not
accept templates by mail or facsimile, nor will InterNic make
changes to the data in Domain name records in response to telephone
calls.
| NOTE |
ISP stands for Internet Service Provider. IP stands for Internet Protocol. |
As an aide to the newcomer, InterNIC has put together a very nice
Registration Template Guide. This guide briefly describes each
template and where to get more information.
| NOTE |
Remember that templates change from time to time. You should ensure that you are using the most current version of a given template. |
The IP address is the way all of the servers keep straight who is who and where they are located. No duplications can be allowed across the Internet for this addressing scheme to work properly. Because of this fact, it is easy to understand why rigid rules must be followed to assign IP address ranges to all parties.
What is happening today is that the ISP requests several large address blocks in the class b level that can then be assigned to its customers. This provides InterNIC a smaller number of low level class c addresses to maintain. Whether you request your address from your ISP or directly from InterNIC, answer the questions on the following template:
REGISTRATION TEMPLATE GUIDE
[URL ftp://rs.internic.net/templates/internet-number-template.txt ]
[08/95]
***************** PLEASE DO NOT REMOVE Version Number****************
Network Version Number: 2.0
****************** Please see attached detailed instructions********* *********
1a. Approximate date of Internet
connection.....................:
1b. Name of Internet access
provider (if known)............:
Technical POC
2a. NIC handle (if known)..........:
2b. Name (Last, First).............:
2c. Title..........................:
2d. Postal address.................:
2e. Phone Number...................:
2f. E-Mailbox......................:
3. Network name...................:
4a. Name of Organization...........:
4b. Postal address of Organization.:
5. Previously assigned addresses..:
Explain how addresses have been
utilized, to include:
5a. Number of hosts.................:
5b. Number of subnets...............:
5c. Subnet mask.....................:
Justification
Host Information
6a. Initially.......................:
6b. Within 1 year...................:
Subnet Information
6c. Initially.......................:
6d. Within one year.................:
7a. Number of addresses requested...:
7b. Additional supporting
justification...................:
If requesting 16 C's or more, you are required to submit the
network topology plan in the format of the example below:
---------------------------------------------------------------------
Subnet# Subnet Mask Max Now 1yr Description
---------------------------------------------------------------------
1.0 255.255.255.224 30 8 16 Network Group (use
1.1 255.255.255.224 30 17 22 Engineering
1.2 255.255.255.224 30 12 12 Manufacturing
1.3 255.255.255.224 30 5 9 Management
1.4 255.255.255.224 30 10 15 Sales
1.5 255.255.255.224 30 7 8 Finance
1.6 255.255.255.224 30 0 0 (spare)
---------------------------------------------------------------------
Totals 210 59 82
---------------------------------------------------------------------
If requesting a Class B or 256 C's (/16 prefix) a network diagram
should also be included with your request.
8. Type of network..................:
INSTRUCTIONS FOR REQUESTING INTERNET (IP) NUMBERS
The internet-number-template.txt must be completed as part of the
application process for obtaining Internet Protocol (IP) Network Numbers.
To obtain one or more Internet numbers, please submit the template
via electronic mail, to HOSTMASTER@INTERNIC.NET. In the subject of the message,
use the words, "IP REQUEST".
Once Registration Services receives your completed application we will send you an
acknowledgment, via electronic mail.
If electronic mail is not available to you, please mail hardcopy to:
Network Solutions
InterNIC Registration Services
505 Huntmar Park Drive
Herndon, VA 22070
-- OR --
FAX to (703) 742-4811
Please do not modify the form nor remove the version number.
European network requests should use the European template located at
(ftp://ftp.ripe.net/ripe/forms/netnum-appl.txt).
Please follow their instructions for submission.
Networks that will be connected/located within the geographic
region maintained by the Asian-Pacific NIC should use the APNIC
template located at
ftp://ftp./apnic/docs/english/apnic-001.txt.
Please follow their instructions for submission.
***PLEASE READ THE FOLLOWING INFORMATION PRIOR TO REQUESTING AN
IP NUMBER FROM THE INTERNIC:
Due to technical and implementation constraints on the Internet routing system and
the possibility of routing overload, certain policies may need to be enforced
by the major transit providers in order to reduce the number of globally advertised routes.
These potential policies may include setting limits on the size of CIDR prefixes
added to the routing tables, filtering of non-aggregated routes, etc.
Therefore, addresses obtained directly from the InterNIC
(non-provider-based, also known as portable) are not guaranteed to be routable
on the Internet.
It is for this reason, you are encouraged to request an IP address
from your service provider. If you have not selected a service provider,
but plan to connect in the future or your network will never be connected to the Internet,
you are encouraged to use IP numbers reserved for non-connected networks
set forth in RFC1597 until you can utilize address space from your chosen Internet provider.
Also, please note, your organization will only be assigned address space for their immediate
to one (1) year requirement. A prefix longer than /24 may be issued if deemed appropriate.
Section 1 - Internet connection
Please supply information on the approximate date of your
connection to the Internet and the name of your Internet
access provider, if known. Again, if you have a service
provider, you should be contacting them for IP addresses.
Section 2 - Technical Point of Contact
The technical POC is the person who tends to the technical
aspects of maintaining the IP addresses. This person should
be able to answer any utilization questions the InterNIC may have.
Each person in the InterNIC database is assigned a "handle" -
a unique tag consisting of the person's initials and a serial
number. This tag is used on records in the database to
indicate a point of contact for a network, domain, or other entity.
If the technical POC's nic handle is unknown, please leave question 2a. blank.
When completing question 2b, place the city, state, and zip code
on a separate line. Use a comma to separate the city and state.
Do not insert a period following the state abbreviation. For example:
Organization address.: Street or PO Box
Herndon, VA 22070
If the organization is in a country other than the United States,
please include the name of the country on the last line by itself.
Contacts must list phone numbers and e-mail addresses.
Section 3 - Network name
Supply the SHORT mnemonic name for the network (up to 12 characters).
This is the name that will be used as an identifier in
internet name and address tables. The only special character that
may be used in a network name is a dash (-). PLEASE DO NOT USE
PERIODS OR UNDERSCORES. The syntax XXXX.com and XXXX.net are not
valid network naming conventions and should only be used when
applying for a domain.
Section 4 - Organization name and postal address
Identify the name and geographic location of the organization
that will be utilizing the network address. Please make
sure your response on 4b is to the right of the colon.
Section 5 - Previously assigned addresses
Please list all IP addresses previously assigned to your entire
organization. Also give the specifics regarding the utilization
of those addresses in questions 5a thru 5c.
Section 6 - Justification
Estimate the size of the network to include the number of hosts
and subnets that will be supported by the network.
A "host" is defined as any device (PC, printer, etc)
that will be assigned an address from the host portion of the network number.
A host may also be characterized as a node or device.
Section 7 - Number of addresses requested
Please state exactly how many addresses you are requesting along
with any additional justification necessary. As stated on the
template, if you are requesting 16 C's or more (/19 prefix) you
will need to complete the network topology plan in the format
shown on the template.
If you are requesting 256 C's or a Class B (/16 prefix) or more,
please include a copy of your network diagram.
Your organization is strongly encouraged to subnet where
feasible.
Section 8 - Type of network
Networks are characterized as being either Research, Educational,
Government-Non Defense or Commercial. Which type is this network?
For further information contact InterNIC Registration Services:
Via electronic mail: HOSTMASTER@INTERNIC.NET
Via telephone: (703) 742-4777
Via postal mail: Network Solutions
InterNIC Registration Service
505 Huntmar Park Drive
Herndon, VA 22070
RECOMMENDED READING (available via anonymous FTP from DS.INTERNIC.NET (198.49.45.10),
or call 1-619-455-4600
Gerich, E. Guidelines for Management of IP Address Space, Ann Arbor, MI:
Merit Network, Inc.; May 1993; RFC 1466. 10 p. (DS.INTERNIC.NET RFC1466.TXT).
Rekhter, Y., Moskowitz. B., Karrenberg, D., de Groot, G.
Address Allocation for Private Internets, IBM Corp., Chrysler Corp.,
RIPE NCC; March 1994; RFC 1597. 8 p. (DS.INTERNIC.NET RFC1597.TXT).
Braden, R.T.; Postel, J.B. Requirements for Internet Gateways. Marina
del Rey, CA: University of Southern California, Information Sciences
Inst.; 1987 June; RFC 1009. 55 p. (DS.INTERNET.NET POLICY RFC1009.TXT).
Internet Engineering Task Force, Braden, R.T. Requirements for Internet
Hosts -- Communication Layers. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; October 1989;
RFC 1122. 116 p. (DS.INTERNIC.NET RFC1122.TXT).
Internet Engineering Task Force, Braden, R.T. Requirements for Internet
Hosts -- Application and Support. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; October 1989;
RFC 1123. 98 p. (DS.INTERNIC.NET RFC1123.TXT).
Internet Activities Board. Internet Official Protocol Standards.
1994 March; RFC 1600. 34p. (DS.INTERNIC.NET POLICY RFC1600.TXT).
[Note: the current version is always available as "STD 1".]
Postel, J.B. Internet Standard Subnetting Procedure.
Stanford, CA: Stanford University; 1995 March; Obsoletes RFC1720
RFC 1780 (DS.INTERNIC.NET RFC1780.TXT)
Postel, J.B. Internet Control Message Protocol. Marina del Rey, CA:
University of Southern California, Information Sciences Inst.; 1981
September; RFC 792. 21 p. (DS.INTERNIC.NET POLICY RFC792.TXT).
Postel, J.B. Transmission Control Protocol. Marina del Rey, CA:
University of Southern California, Information Sciences Inst.; 1981
September; RFC 793. 85 p. (DS.INTERNIC.NET POLICY RFC793.TXT).
Postel, J.B. User Datagram Protocol. Marina del Rey, CA: University
of Southern California, Information Sciences Inst.; 1980 August 28;
RFC 768. 3 p. (DS.INTERNIC.NET POLICY RFC768.TXT).
Postel, J.B. Internet Protocol. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; 1981 September; RFC
791. 45 p. (DS.INTERNIC.NET POLICY RFC791.TXT).
Reynolds, J.K.; Postel, J.B. Assigned Numbers. Marina del Rey, CA:
University of Southern California, Information Sciences Inst.;
1994 October; RFC 1700. (DS.INTERNIC.NET POLICY RFC1700.TXT).
(Obsoletes RFC1340)
The Domain Name your computers operate under is the next most important piece of information you must have to place your server on the Internet. Domain names are used by many different kinds of software to direct queries and searches to the correct place.
Domain names are the equivalent of street addresses in the computer world. Through the use of these names, the InterNIC is able to manage and understand who is doing what and where on the Internet. Without managed and unique domain names on the Internet, it would be impossible to find any valuable infor-mation. Through this naming scheme, established early in the development of the Internet, you can create graphical displays of all the computers on the Internet. The Domain name has standard parts embedded in it to identify the country of origin, for example, US for the United States, the type of organization, com for commercial for-profit company, and the actual domain name, IBM.
This name is cross-linked in several name servers which match up IP addresses to domain names and identify the correct routing for packets coming across the Internet. The following template is the registration template for InterNIC to register your Domain Name.
REGISTRATION TEMPLATE GUIDE
[ URL ftp://rs.internic.net/templates/domain-template.txt ] [ 5/96 ] *************** Please DO NOT REMOVE Version Number ************** Domain Version Number: 3.0 **************** Please see attached detailed instructions ***************** ******** Only for registrations under ROOT, COM, ORG, NET, EDU, GOV ******** Authorization 0a. (N)ew (M)odify elete....: 0b. Auth Scheme................: 0c. Auth Info..................: 1. Purpose/Description........: 2. Complete Domain Name.......: Organization Using Domain Name 3a. Organization Name..........: 3b. Street Address.............: 3c. City.......................: 3d. State......................: 3e. Postal Code................: 3f. Country Code...............: Administrative Contact 4a. NIC Handle (if known)......: 4b. (I)ndividual (R)ole........: 4c. Name.......................: 4d. Organization Name..........: 4e. Street Address.............: 4f. City.......................: 4g. State......................: 4h. Postal Code................: 4i. Country Code...............: 4j. Phone Number...............: 4k. Fax Number.................: 4l. E-Mailbox..................: Technical Contact 5a. NIC Handle (if known)......: 5b. (I)ndividual (R)ole........: 5c. Name.......................: 5d. Organization Name..........: 5e. Street Address.............: 5f. City.......................: 5g. State......................: 5h. Postal Code................: 5i. Country Code...............: 5j. Phone Number...............: 5k. Fax Number.................: 5l. E-Mailbox..................: Billing Contact 6a. NIC Handle (if known)......: 6b. (I)ndividual (R)ole........: 6c. Name.......................: 6d. Organization Name..........: 6e. Street Address.............: 6f. City.......................: 6g. State......................: 6h. Postal Code................: 6i. Country Code...............: 6j. Phone Number...............: 6k. Fax Number.................: 6l. E-Mailbox..................: Primary Name Server 7a. Primary Server Hostname....: 7b. Primary Server Netaddress..: Secondary Name Server(s) 8a. Secondary Server Hostname..: 8b. Secondary Server Netaddress: Invoice Delivery 9. (E)mail (P)ostal...........:An initial charge of $100.00 USD will be made to register the Domain name. This charge covers any updates required during the first two (2) years. The Billing Contact listed in Section 6 will be invoiced within ten (10) days of Domain name registration. For detailed information on billing, see: ftp://rs.internic.net/billing/billing-procedures.txt http://rs.internic.net/guardian/
The party requesting registration of this name certifies that, to her/his knowledge, the use of this name does not violate trademark or other statutes.
Registering a Domain name does not confer any legal rights to that name and any disputes between parties over the rights to use a particular name are to be settled between the contending parties using normal legal methods. See RFC 1591 available at: ftp://rs.internic.net/policy/rfc1591.txt
By applying for the Domain name and through the use or continued use of the Domain name, the applicant agrees to be bound by the terms of NSI's then current Domain name policy (the 'Policy Statement') which is available at: ftp://rs.internic.net/policy/internic/internic-domain-4.txt
(If this application is made through an agent, such as an Internet Service Provider, that agent accepts the responsibility to notify the applicant of the conditions on the registration of the Domain name and to provide the applicant a copy of the current version of the Policy Statement, if so requested by the applicant.) The applicant acknowledges and agrees that NSI may change the terms and conditions of the Policy Statement from time to time as provided in the Policy Statement.
The applicant agrees that if the use of the Domain name is challenged by any third party, or if any dispute arises under this Registration Agreement, as amended, the applicant will abide by the procedures specified in the Policy Statement.
This Registration Agreement shall be governed in all respects by and construed in accordance with the laws of the United States of America and of the State of California, without respect to its conflict of law rules. This Registration Agreement is the complete and exclusive agreement of the applicant and NSI ("parties") regarding Domain names. It supersedes, and its terms govern, all prior proposals, agreements, or other communications between the parties. This Registration Agreement may only be amended as provided in the Policy Statement.
Once you have your Domain name registered, you are ready to set up your server and connect it to the Internet. This name must be maintained over the years with the annual maintenance fee, so be sure the administrative person listed stays current and the address stays current for billing purposes. Because of the large number of users on the Internet, it is impossible for the InterNIC to track down everyone who does not respond to the billings, and they are forced to simply drop the name registration.
There are four other types of registration that you can use with the InterNIC if your particular server implementation requires them. The other four are Contact Registration, Host Registration, Autonomous System Number Registration, and Inverse-Addressing Registration. Each of these satisfies a unique set of requirements, which should be considered before you implement your server to see if they apply to your implementation.
This type of registration is really an extension to the normal contact that must be indicated on the Domain Name and IP address registration. The primary reason it is a separate registration template is that contacts tend to change very frequently on the various registrations because of personnel changes. The InterNIC did not want customers to have to fill out all the information again on a Domain Name template just to change the contact. The only problem this causes is that trying to validate electronically that a contact change is really valid can be very tricky.
Because of this need to have a more secure way to implement the contact change template, InterNIC introduced the Guardian system. This system provides several ways to electronically validate the originating parties' authority to change a contact registration without asking for blood samples.
Refer to the following section for a detailed explanation of the guardian system:
What's this Guardian thing, anyway?
Put simply, the InterNIC hopes to protect your domain information from unauthorized modifications. The plan we've implemented is called Guardian. Here's how it works:
(The same applies to registering a host: Initial registration of the host should be done as part of a domain name registration. However, any changes in the future to that host information must be requested using a host template.)
The following is the template you must fill out for the contact registration change or addition.
REGISTRATION TEMPLATE GUIDE
[ URL ftp://rs.internic.net/templates/contact-template.txt ] [ 5/96 ] ************ Please DO NOT REMOVE Version Number ********************** Contact Version Number: 1.0 **************** Please see attached detailed instructions ******************* Authorization 0a. (N)ew (M)odify elete.: 0b. Auth Scheme.............: 0c. Auth Info...............: Contact Information 1a. NIC Handle..............: 1b. (I)ndividual (R)ole.....: 1c. Name....................: 1d. Organization Name.......: 1e. Street Address..........: 1f. City....................: 1g. State...................: 1h. Postal Code.............: 1i. Country Code............: 1j. Phone Number............: 1k. Fax Number..............: 1l. E-Mailbox...............: Notify Information 2a. Notify Updates..........: 2b. Notify Use..............: Authentication Information 3a. Auth Scheme.............: 3b. Auth Info...............: 3c. Public (Y/N)............: A file containing examples of completed templates is available at: ftp://rs.internic.net/templates/contact-template-examples.txt
This is the registration of a host computer that is usually thought of as a name server computer. This simply means a computer which matches up IP addresses with computer names within your network for routing purposes. Some companies will maintain many host servers with dynamic addressing and static addressing. If these host are to be made available to other users on the Internet, they must beregistered in the host computers maintained by InterNIC on the Internet.
The following is the template you must fill out for registration of a host computer. You must always have a unique IP address to host name relationship for the registration to be accepted.
REGISTRATION TEMPLATE GUIDE
[ URL ftp://rs.internic.net/templates/host-template.txt ] [ 5/96 ] **************** Please DO NOT REMOVE Version Number ****************** Host Version Number: 1.0 ************* Please see attached detailed instructions *************** Authorization 0a. (N)ew (M)odify elete.: 0b. Auth Scheme.............: 0c. Auth Info...............: Host 1a. NIC Handle (if known)...: 1b. Host Name...............: 1c. IP Address..............: Contact 2a. NIC Handle (if known)...: 2b. (I)ndividual (R)ole.....: 2c. Name....................: 2d. Organization Name.......: 2e. Street Address..........: 2f. City....................: 2g. State...................: 2h. Postal Code.............: 2i. Country Code............: 2j. Phone Number............: 2k. Fax Number..............: 2l. E-Mailbox...............:
The Autonomous System (AS) is used for exchanging external routing information with other ASes through an exterior routing protocol. It is a connected group of IP networks with a single and clearly defined routing policy.
Unique Autonomous System Numbers (ASNs) are required for specific ASes. However, due to the finite number of available ASNs, care must be taken to determine which sites require unique ASNs and which do not. This is a very specialized type of network requirement and rarely has an impact on the server, unless there is a conflict between the groups of IP networks.
The template for registration follows:
REGISTRATION TEMPLATE GUIDE
[URL ftp://rs.internic.net/templates/asn-template.txt ] [01/96] ************* PLEASE DO NOT REMOVE Version Number ****************** ASN Version Number: 1.0 **************** Please see attached detailed instructions ****************** One of the following conditions must be satisfied before receiving an Autonomous System Number: a) Unique Routing Policy Please explain how your routing policy is different from your provider. b) Multi-homed Site If your organization is currently multi-homed, please explain exactly how you are connected to the Internet. 0. (N)ew (M)odify elete.: 1. Autonomous System Name..: Organization Using ASN 2a. Organization Name.......: 2b. Street address..........: 2c. City....................: 2d. State...................: 2e. Postal Code.............: 2f. Country.................: Technical Contact 3a. NIC handle (if known)...: 3b. Name (Last, First)......: 3c. Street address..........: 3d. City....................: 3e. State...................: 3f. Postal Code.............: 3g. Country.................: 3h. Phone Number............: 3i. E-Mailbox...............:
There is a special domain on the Internet that supports IP address to computer name matching which is referred to as Inverse-addressing. To register your computer within this domain, you must submit this registration form. This is a very valuable service to some companies because it enables users and applications to connect to a server by its name without having to have the physical address. This makes getting access to these servers much easier for the average user as well as the normal application.
One final benefit that Inverse-addressing provides is the ability to change out machines without having to worry about people and applications not getting connected.
The template for this registration follows:
REGISTRATION TEMPLATE GUIDE
[ URL ftp://rs.internic.net/templates/in-addr-template.txt ] [ 06/95 ]
**************** Please DO NOT REMOVE Version Number ******************
IN-ADDR Version Number: 1.0
************* Please see attached detailed instructions ***************
Registration Action Type
0. (N)ew (M)odify elete:
Network Information
1a. Network Name..................:
1b. Start of Network Block........:
1c. End of Network Block..........:
2a. Name of Organization..........:
2b. Postal address of Organization:
Technical Contact
3a. NIC Handle (if known).........:
3b. Name (Last, First)............:
3c. Organization..................:
3d. Postal Address................:
3e. Phone Number..................:
3f. E-Mail Address................:
Primary Name Server
4a. Primary Server Hostname.......:
4b. Primary Server Netaddress.....:
Secondary Name Server(s)
5a. Secondary Server Hostname.....:
5b. Secondary Server Netaddress...:
6. Comments......................:
This chapter wraps up the preliminary information you need to get started with your Internet Information Server implementation. From this chapter, we move into Chapter 5 "Internal Architecture of IIS." For further information on the topic of Internet connection and registration, refer to: