As per Relevance of the word registration, we have this rfc below:
Network Working Group S.
Request for Comments: 1400 Network Solutions, Inc
March 1993
Transition and
of the Internet Registration
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
As a result of the NREN NIS award by National Science Foundation
non-DDN registration services will soon be transferred from the
NIC to the new Internet Registration Service, which is a part of
entity referred to as the InterNIC. References in this document
the InterNIC apply to the Registration Services portion only
Internet registration services are gradually transitioning to
InterNIC. We expect that the full transition will be accomplished
April 1, 1993. During this transitional period, EMail, Fax, and U.S
mail received at either site will be processed. DDN users
continue to receive full registration support from the DDN NIC,
the transition should be transparent to them. DDN users
continue to send registration requests to hostmast@nic.ddn.mil (IP
.mil domain, inaddr for 26.x.x.x) or registrar@nic.ddn.mil (
registrations or TAC card requests) using the DISA
registration forms
From now through March 31, 1993, non-DDN Internet
requests will be handled as follows
The current DDN NIC registration templates may be filled out
submitted to either hostmaster@internic.net
hostmaster@nic.ddn.mil through March 31. The new
templates will be accepted effective April 1, 1993, but not
that time
Telephone support: 1-800-365-DNIC
1-703-802-4535 (Washington DC metro area
Williamson [Page 1]
RFC 1400 Transition of Registration Services March 1993
Mail questions and registration templates to
Government Systems Inc
Attn: Network Information
14200 Park Meadow Dr
Suite 200
Chantilly, VA 2200
Effective April 1, 1993, non-DDN Internet requests will be handled
described below
New registration requests should be sent to autoreg@internic.
using the new template. Old templates sent
autoreg@internic.net will be returned with the parsing
messages and the new form attached. Old templates mailed
hostmaster@interic.net will be accepted through June 30, 1993.
After that date, templates in the old format will be returned
the sender with the new template attached
Telephone support: 1-800-444-4345 or 619-455-4600
1-703-742-4777 (Registration service only
(Washington DC metro area
Mail questions and registration templates to
Network Solutions, Inc
Attn: InterNIC Registration
505 Huntmar Park
Herndon, VA 22070
In an effort to keep those who are likely to submit a high volume
registration requests informed during the transition period
information regarding Internet registration issues will
distributed via the mail list rs-info@internic.net.
subscription requests to
rs-info-request@internic.net
Information on the location of the new autoreg templates and how
retrieve them will be sent to those who have subscribed to this list
Comments are solicited. The new registration templates have
modified to facilitate automatic processing and to remove all DDN
specific references
WHOIS services will be available at both the DDN NIC and
sites
Williamson [Page 2]
RFC 1400 Transition of Registration Services March 1993
whois.nic.ddn.mil (192.112.36.5)
whois.internic.net (198.41.0.5)
Effective April 1, 1993, only DDN information will be available
whois.nic.ddn.mil. The WHOIS service available
whois.internic.net will contain all information on IP addresses
domains, and ASNs. The WHOIS service available from
whois.internic.net will contain individual user records only
those who serve as a Point of Contact for an active node. Those
are interested in establishing a whois service for information
individual users (e.g., for Internet hosts or campus networks)
encouraged to participate in one of the many distributed WHOIS-
information projects
Root zone files will be available at both sites through March 31,
1993. After that time, the root zone file will be available
from ftp.rs.internic.net
After the transition, the host.txt file will be available only
nic.ddn.mil and hosts.txt will include ONLY MILNET HOSTS. On
1, 1993, a new root DNS server will be placed in service. It will
available at ns.internic.net ( 198.41.0.4 ).
The T1 service currently available to the DDN NIC will
disconnected by June 1, 1993. This will leave only 56K access to
DDN NIC site. Excessive traffic to this site after that date
cause congestion. Therefore, it is important that all
registration data be directed to the new InterNIC site. The
registration services facility will be connected to SuraNET via T
around March 10, 1993.
Automated Internet registration services will be available from
InterNIC registration service host. This new automated system
allow more accurate and timely processing of registration requests
The basic functions/features of the new automated
process (autoreg) are outlined below
* Requestor sends a completed new template
autoreg@internic.net
* The mailserver/parser on the InterNIC registration host
the template and makes a quick check of all
information (such as Domain name conflicts). The
then sends an E-mail verification or rejection with error
back to the requestor
* After receiving the verification form for review, the
should ensure that the information was interpreted correctly by
Williamson [Page 3]
RFC 1400 Transition of Registration Services March 1993
parser. If the information is correct, the requestor returns
verify form to verify@internic.net. If the information is
correct, the requestor should make the necessary corrections
returning the form. If a rejection was received the
must make the necessary adjustments and resend the
request to autoreg@internic.net for processing
* On receipt of a corrected verification form from the
requestor, the data will be rechecked and a new verification
will be sent. Once a good verification has been received
Registration Services, the request will be released for
processing by the InterNIC registration staff
NOTE: If the requestor does not return the verification form to
InterNIC within seven days after it is mailed, the
registration request will expire, and it must be resubmitted
Information on the status of all registration requests will
available to users via two methods. The first method employs
"finger" utility. The finger utility is executed specifying
"trouble ticket" (tt) number returned with the registration
verification/ confirmation message
Example: finger tt-930303.1034@rs.internic.
Users will also be able to obtain status information by connecting
rs.internic.net via telnet and executing the "status "
command. Status information will appear as follows
[BEGIN SCRIPT]__________________________________________________________
> finger tt-930303.1034@rs.internic.
[rs.internic.net
Retrieving information on Ticket 930303.1034. Please wait...
Ticket Number: 930303.1034 Ticket Status:
Ticket Type: reg/domain Ticket Source:
Ticket Scope: Site/Line
Ticket Owner: autoreg Problem Fixer:
Ticket Opened: 03/03/93 14:47
Problem Description
register internic.
Williamson [Page 4]
RFC 1400 Transition of Registration Services March 1993
Problem Solution
For more information, please contact the InterNIC
Center at hostmaster@internic.net or (703) 742-4777. Thanks
[END SCRIPT]____________________________________________________________
Other services will also be available via telnet to rs.internic.net
The interface is similar to the telnet service currently offered
the DDN-NIC. However, the commands used on the InterNIC system
slightly different. The services that will be available via
are: WHOIS, Gopher, wais, finger, and status
Below is a short scripted session on the new InterNIC
host
[BEGIN SCRIPT]__________________________________________________________
% telnet rs.internic.
Trying 198.41.0.5 ...
Connected to rs.internic.net
Escape character is '^]'.
SunOS UNIX (rs) (ttyp4)
************************************************************************
* -- InterNIC Network Registration Center --
*
* For gopher, type: GOPHER
* For wais, type: WAIS
* For the *original* whois type: WHOIS
* For the X.500 whois DUA, type: X500WHOIS
*
* For user assistance call (800) 444-4345 or (703) 742-4777
* Please report system problems to ACTION@rs.internic.
************************************************************************
Cmdinter Ver 1.3 Wed Mar 10 11:23:05 1993
InterNIC > ?
Command, one of the
DATE FINGER HELP KERMIT
LOGOUT STATUS WHOIS GOPHER
X500
InterNIC >
Wed Mar 10 11:23:09 EST 1993
Williamson [Page 5]
RFC 1400 Transition of Registration Services March 1993
InterNIC >
Connecting to the rs Database . . . . . .
Connected to the rs
InterNIC WHOIS Version: 1.0 Wed, 10 Mar 93 11:23:19
Whois: !internic-
Network Solutions, Inc. (INTERNIC-DOM
505 Huntmar Park
Herndon, VA 22070
Domain Name: INTERNIC.
Administrative Contact
Zalubski, John (JZ7) zalubskj@INTERNIC.
(703) 802-8462
Technical Contact, Zone Contact
Kosters, Mark A. (MAK21) markk@INTERNIC.
(703) 802-8484
Record last updated on 10-Feb-93.
Domain servers in listed order
REG.INTERNIC.NET 192.153.247.80
NOC.CERF.NET 192.153.156.22
Whois:
InterNIC >
Wed Mar 10 11:24:54 1993
Connection closed by foreign host
%
[END SCRIPT]____________________________________________________________
Williamson [Page 6]
RFC 1400 Transition of Registration Services March 1993
Summary of InterNIC registration services information
rs.internic.net 198.41.0.5
ns.internic.net 198.41.0.4
General telephone support: 1-800-444-4365
Registration support: 703-742-4777
Mail address
Network Solutions Inc
ATTN: InterNIC Registration
505 Huntmar Park Dr
Herndon, VA 22070
rs-info@internic.net Registration information mail
rs-info-request@internic.
hostmaster@internic.net Registration questions and
autoreg@internic.net Automatic registration
finger tt-XXXXXX.XXXX@rs.internic.net To check status of
Security
Security issues are not discussed in this memo
Author's
Scott
Network Solutions, Inc
505 Huntmar Park
Herndon, VA 22070
Phone: (703) 742-4820
EMail: scottw@internic.
Williamson [Page 7]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
