[vcf-midatlantic] domain-template.txt
Dave McGuire
mcguire at neurotica.com
Thu Sep 8 12:10:38 EDT 2016
Here's a copy of domain-template.txt, for any interested parties:
--------------------------------
[ URL ftp://rs.internic.net/templates/domain-template.txt ] [ 07/95 ]
******************* Please DO NOT REMOVE Version Number ********************
Domain Version Number: 1.0
**************** Please see attached detailed instructions *****************
******** Only for registrations under ROOT, EDU, GOV, COM, NET, ORG ********
0. (N)ew (M)odify (D)elete.:
1. Purpose/Description.....:
2. Complete Domain Name....:
3a. Organization name.......:
3b. Organization address....:
4. Operational Date........:
Administrative Contact
5a. NIC Handle (if known)...:
5b. Name (Last, First)......:
5c. Organization............:
5d. Postal Address..........:
5e. Phone Number............:
5f. E-Mailbox...............:
Technical/Zone Contact
6a. NIC Handle (if known)...:
6b. Name (Last, First)......:
6c. Organization............:
6d. Postal Address..........:
6e. Phone Number............:
6f. E-Mailbox...............:
Primary Name Server
7a. Prime Server Hostname...:
7b. Prime Server Netaddress.:
7c. Prime Server Hardware...:
7d. Prime Server Software...:
Secondary Name Server(s)
8a. Second Server Hostname..:
8b. Second Server Netaddress:
8c. Second Server Hardware..:
8d. Second Server Software..:
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)
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.domain.policy.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 acknowledge and agree 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 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.
--------------------------------- cut here ---------------------------------
GENERAL INSTRUCTIONS
Use the form above for registering new domain names, for making changes
to existing domain name records and for removing a domain name from the
InterNIC database and root servers. The form, and only the form, should
be sent via e-mail to HOSTMASTER at INTERNIC.NET Please do not send
hardcopy registrations to the InterNIC. Your provider will be able to
send e-mail applications if you are not connected.
In the Subject of the message, use the words, "NEW DOMAIN", "MODIFY DOMAIN",
or "REMOVE DOMAIN" as appropriate, followed by the name of the domain to
assist in sorting and locating incoming registration requests.
In response to the submission of a form, you should receive an auto-reply
with a ticket number. Use the ticket number in the Subject of any messages
you send regarding that registration action. When the registration is
completed you will receive a notification via e-mail.
If you regularly submit domain applications, you will note two changes
in the registration form. Section 0 has been added to indicate the nature
of the registration action, and the Purpose section of the registration has
been moved from the end of the form to Section 1. These changes were made
to further automate the registration process and to allow the person
reviewing the registration to more easily see the Purpose section.
The goal of these changes is to improve the quality and responsiveness
of service to you.
Please do not modify the form nor remove the version number. The computer
program that scans and parses the form is looking for section numbers,
followed by a period, followed by a colon. Information following the
colon is compared with and inserted into the database as appropriate.
Please send only one form per message.
When completing the form, make use of "whois" at rs.internic.net
to check to see if domain names, organization names, people, and
name servers have been registered. Use the information in the database
where appropriate. This will minimize the number of registrations that
are returned for incomplete or inaccurate information.
The instructions for completing each field are in the following three
sections - one each for NEW, MODIFY and DELETE. The interpretation of
missing or blank fields can vary between the New and Modify registration
actions. Please read the instructions carefully and make sure the form
is properly completed to accomplish the action you desire.
REGISTERING A NEW DOMAIN NAME
Section 0 - Registration Action Type
Following the colon, place the character "N" or the word "New"
to indicate this is a NEW registration. The transfer of a name
from one organization to another is considered a new registration.
If the intent is to effect a transfer, clearly indicate this in
Section 1 and include a statement from the current holder of the
name that it is being transferred.
Section 1 - Purpose of Registration
Briefly describe the organization and/or the purpose for which this
domain name is being registered. The description should support the
choice of top-level domain in Section 2. If the domain name is for
an organization that already has a domain name registered, describe
the purpose of this domain and why the additional name is needed.
Indicate why existing names cannot be used or why the proposed second-
level name cannot be used as a third-level name under a domain name
that is already registered.
Section 2 - Complete Domain Name
Top-level country domains may be registered by inserting the
two-letter country code in this section. See RFC1591 for the
duties and responsibilities of top-level domain administrators.
For second-level domain names under EDU, GOV, COM, NET, or ORG,
insert the two-part name of the domain you wish to register, for
example, ABC.COM. The total length of the two-part name may be up
to 24 characters. The only characters allowed in a domain name are
letters, digits and the dash (-), (see RFC952.) Consult RFC1591 to
determine the most appropriate top-level domain to join. Briefly:
EDU is for 4-year, degree granting institutions.
GOV is for United States federal government agencies.
COM is for commercial, for-profit organizations.
NET is for network infrastructure machines and organizations.
ORG is for not-for-profit and non-profit organizations.
US state and local government agencies, schools, libraries, museums,
and individuals should register under the US domain. See RFC1480 for
a complete description of the US domain and registration procedures.
Section 3 - Organization Using the Domain Name
The domain name is considered to be registered to an organization,
even if the "organization" is an individual. It is important in this
section to list the name and address of the end-user organization,
not the provider organization.
If the organization has the same name as one that is already
registered, explain this in Section 1 above.
When completing item 3b, place the city, state, and zip code on
a separate line. Use a comma to separate the city and state.
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.
For example:
Organization address.: Street or PO Box
Montreal, QC H2S 2C8
Canada
Section 4 - Operational Date
Insert the date in YY/MM/DD format when you expect the domain name
servers will be connected and responding to domain name system (DNS)
queries for the requested domain name. The name servers should be
operational at the time of registration and we may reject the
registration if is not answering authoritatively for the domain
submitted.
Section 5 - Administrative Contact
The administrative contact is the person who can speak on behalf
of the organization listed in Section 3. This person should be
able to answer non-technical questions about the organization's
plans for the name, and procedures for establishing sub-domains,
and should be able to represent the organization regarding use of
the name. See RFC1032 for more detail on administrative contacts.
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 domain name, network, name server or
other entity. Each person should have only one handle.
If the person's handle is known, insert just the handle in
item 5a and leave the rest of Section 5 blank.
If a person's handle is unknown or the person has never been
registered, leave item 5a blank. The registration software
will check for an existing user record. If a matching user
record is found, the handle will be put into field 5a. The
user's database record will be updated with any new information
on the template.
Use the same format for specifying the postal address as described
in Section 3 above; placing city, state zip code or country name
on the last line of the multi-line address. The two-letter country
code may be used in lieu of the country name.
Contacts must list phone numbers and have e-mail addresses.
If an e-mail address is not given, Postmaster at domain.name (the
domain name being registered) will be assigned. Please make an
effort to determine what the person's e-mail address will be
so that updates are not required shortly after registration.
Section 6 - Technical and Zone Contact
The domain technical/zone contact is the person who tends to
the technical aspects of maintaining the domain's name server,
resolver software, and database files. S/He keeps the name
server running, and interacts with technical people in other
domains to solve problems that affect the domain. The Internet
Service Provider often performs this role.
The procedures for completing Section 6 are the same as for
Section 5. If Section 6 is left blank, the information from
Section 5 will be assumed and vice-versa.
Section 7 - Primary Name Server
Domains must provide at least two independent servers for
translating names to addresses for hosts in the domain. The
servers should be in physically separate locations and on
different networks if possible. The servers should be active
and responsive to DNS queries BEFORE this application is
submitted. Incomplete information in sections 7 and 8 or
inactive servers will result in delay of the registration.
As a minimum, complete 7a and 7b. The registration software
makes a cross check between the host name given and the IP
addresses given to see if there are matches with either in the
database. If a match with an IP number in the database is
found, the name in the database will be assumed. Neither the
name nor number of a registered name server will be changed as
a result of a new domain registration. A Modify registration
request must be sent to change either of these values.
Please provide the fully-qualified name of the machine that is
to be the name server; for example: "machine.domainame.com"
not just "machine"
Section 8 - Secondary Name Server(s)
The same procedures for specifying primary servers apply to
secondary servers. If several secondary servers are required,
copy Section 8 as many times as needed. Do not renumber or
change the copied section.
MODIFYING A DOMAIN NAME RECORD
Changing an existing record is done by replacement. That is, the
contents of various fields in the database are replaced with new
information from the form. If the modification involves first
registering a person or name server that is not in the database,
the instructions for completing Sections 5-8 "REGISTERING A NEW
DOMAIN NAME" apply. Use "whois" if you are unsure about the current
information for a domain, name server, or individual.
Changes will be made if it appears to the operator that the modification
request has come from a "reasonable" source. This source could be from
a listed contact for the domain, from others in the same organization,
from the current provider, or from a new provider that is about to
provide support for the domain.
Notification of the change and the approximate time it will take
effect will be sent to:
the requester and,
if contacts are changing, to both old and new contacts and,
if name servers are changing, to both technical contacts for
the domains in which the old and new primary name servers reside.
This dissemination of change information is to assure that all
parties involved are aware and concur with the change.
Transfer of a name from one organization to another is considered a
new registration. See, "REGISTERING A NEW DOMAIN NAME."
Section 0 - Registration Action Type
Following the colon, place the character "M" or the word "Modify"
to indicate this is a change to an existing registration. Transfer
of a name from one organization to another is considered a new
registration. See, "REGISTERING A NEW DOMAIN NAME."
Section 1 - Purpose of Registration
Briefly describe the purpose of the modification. If the intent is
to change either the name or the IP address of name servers, make this
very clear, otherwise changes to name servers will not be made.
If you wish to change the name of the domain itself, file a separate
NEW registration and a DELETE registration when you are ready to
have the old name removed. Make it clear in this section that you
are changing from one domain name to another and estimate how long
you will need the old domain name.
Section 2 - Complete Domain Name
Insert the two-part name of the domain name you wish to modify,
for example, ABC.COM. This section must be completed, even
if you are making minor changes, like the phone number of a
point of contact, for example.
Section 3 - Organization Using the Domain Name
The domain name is considered to be registered to an organization,
even if the "organization" is an individual. Therefore, a change
in the organization name should be explained in Section 1. Transfer
of a name from one organization to another is considered a new
registration. See, "REGISTERING A NEW DOMAIN NAME."
Section 4 - Operational Date
This section may be left blank.
Section 5 - Administrative Contact
If a handle is given in item 5a, the database will be updated with any
information on the form in items 5b through 5e. If any item is missing or
blank, the corresponding information in the database will not be altered.
If no handle is given, the database will be searched to see if the
person is already registered. If so, the person's record will be
updated with any new information on the form. If not registered,
the person will be entered into the database and assigned a handle.
The handle will be attached to the domain name record, thus replacing
the old individual with the new.
Section 6 - Technical and Zone Contact
If it is desired to replace the technical/zone contact with another
individual, both Sections 5 and 6 must be completed even if they are
the same person.
Section 7 - Primary Name Server
If any changes in name servers are being made, provide a complete
list of name servers (both primary and secondary). The list in the
application will replace the list in the database.
If the intention is to change the name or IP address of a name server,
clearly state that in Section 1 above. The default is to NOT change
either of these values unless so instructed in Section 1.
Section 8 - Secondary Name Server(s)
If any changes in name servers are being made, provide a complete
list of name servers (both primary and secondary). The list in the
application will replace the list in the database.
DELETING A DOMAIN NAME RECORD
A request to remove a registered domain name from the database may come
from the administrative or technical contact for the domain, from a
provider who is no longer supporting the name, or from an interested
third party who has detected that the name is not active. In the latter
case, the InterNIC will make further inquires before removing the name.
When the name is removed, it will no longer be visible via whois,
wais, gopher, or Web browsers that query the InterNIC database. It
will also be removed from the root name servers on the subsequent update.
Notification of the deletion and the approximate time it will take
effect will be sent to the requestor, the contacts currently listed,
and to the technical contact for the domain in which the primary name
server resides, if different from the domain being deleted.
When a name is transferred from one organization to another, the InterNIC
will first delete the existing record and then process a new registration.
Section 0 - Registration Action Type
Following the colon, place the character "D" or the word "Delete"
to indicate this is a deletion of an existing registration.
Section 1 - Purpose of Registration
Briefly state the reason for removing the name. If you are an
interested third party, describe your attempts to reach the
people in the domain and their response, or lack thereof.
If you feel additional records, such as point(s) of contact or
name servers should also be deleted, state that in this section.
These will not be automatically removed. The InterNIC will
check further to see if they are used on other domain, network,
or autonomous system number records before removing them.
Section 2 - Complete Domain Name
Insert the two-part name of the domain name you wish to have removed.
Section 3 - Section 8
These sections should be left blank or removed.
RECOMMENDED READING
Albitz, P., C. Liu, "DNS and Bind" Help for UNIX System Administrators,
O'Reilly and Associates, Inc., October 1992.
Postel, J., "Domain Name System Structure and Delegation". Marina del
Rey, CA: University of Southern California, Information Sciences
Inst.; 1994 March; RFC 1591. 7 p.
<URL: ftp://rs.internic.net/policy/rfc1591.txt>
Cooper, Postel, "The US Domain". Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; 1992 December;
RFC 1480. 31 p.
<URL: ftp://rs.internic.net/policy/rfc1480.txt>
Stahl, M.K. Domain Administrators Guide. Menlo Park, CA: SRI
International, DDN Network Information Center; 1987 November;
RFC 1032. 14 p.
<URL: ftp://rs.internic.net/policy/rfc1032.txt>
Lottor, M. Domain Administrators Operations Guide. Menlo Park, CA:
SRI International, DDN Network Information Center; 1987 November;
RFC 1033. 22 p.
<URL: ftp://rs.internic.net/policy/rfc1033.txt>
Mockapetris, P. Domain Names - Concepts and Facilities. Marina del
Rey, CA: University of Southern California, Information Sciences
Inst.; 1987 November; RFC 1034. 55 p.
<URL: ftp://rs.internic.net/policy/rfc1034.txt>
Mockapetris, P. Domain names - Implementation and Specification.
Marina del Rey, CA: University of Southern California, Information
Sciences Inst.; 1987 November; RFC 1035. 55 p.
<URL: ftp://rs.internic.net/policy/rfc1035.txt>
Mockapetris, P. DNS Encoding of Network Names and Other Types. Marina
del Rey, CA: University of Southern California, Information Sciences
Inst.; 1989 April; RFC 1101. 14 p.
<URL: ftp://rs.internic.net/policy/rfc1101.txt>
--------------------------------
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
More information about the vcf-midatlantic
mailing list