As per Relevance of the word response, we have this rfc below:
Ken Harrenstien RFC-811
Vic White 1 March 1982
Elizabeth
Network Information
SRI
HOSTNAMES
The NIC Internet Hostnames Server is an NCP/TCP-based
information program and protocol running on the SRI-
machine. It is one of a series of ARPANET/Internet
services maintained by the Network Information Center (NIC)
SRI International on behalf of the Defense
Agency (DCA). The function of this particular server is
deliver machine-readable name/address information
networks, gateways, hosts, and eventually domains, within
internet environment. As currently implemented, the
provides the information outlined in the DoD Internet
Table Specification (RFC 810).
QUERY/RESPONSE
The name server accepts simple text query requests of the
<argument(s)> []
where square brackets ("[]") indicate an optional field.
command key is a keyword indicating the nature of the request
The defined keys are explained below
The response, on the other hand, is of the
<response key> : response
where <response key> is a keyword indicating the nature of
response, and the rest of the response is interpreted in
context of the key
COMMAND/RESPONSE
The currently defined keywords are
Command Keys
HNAME (find entry with given name
HADDR (find entry with given address
ALL (return entire host table
[Page 1]
1 March 1982
RFC 811 Hostnames
Response Keys
ERR (entry not found, nature of error follows
NET (entry found, rest of entry follows
GATEWAY (entry found, rest of entry follows
HOST (entry found, rest of entry follows
BEGIN (followed by multiple entries
END (done with BEGIN block of entries
More keywords will be added as new needs are recognized.
more detailed description of the allowed requests/
will follow
To access this server from a program, connect to service
(SRI-NIC
TCP: port 101
NCP: socket 101 decimal for
send the information query, and await the response
Note: Care should be taken to interpret the nature of
reply (e.g, single record or multiple record), so that
confusion about the state of the reply results. An "ALL
request will likely return several hundred or more records
all types (see RFC 810), whereas "HNAME" or "HADDR"
usually return one HOST record, or "BEGIN:", list of
records, "END:", if there is more than one match
QUERY/RESPONSE
1. HNAME Query - Given a name, find the entry or entries
the name. For example
HNAME SRI-NIC ;where is a
return
linefeed, and 'SRI-NIC' is
host
The likely response is
HOST : 10.0.0.73 : SRI-NIC,NIC : FOONLY-F3 : TENEX : NCP :
A response may stretch across more than one line
Continuation lines always begin with at least one space
For example
HOST : 10.0.0.73 : SRI-NIC,NIC : FOONLY-F3 : TENEX : NCP :
[Page 2]
1 March 1982
Hostnames Server RFC 811
2. HADDR Query - Given an internet address (as specified
796) find the entry or entries that match that address
For example
HADDR 10.0.0.73 ;where is a
return
linefeed, and '10.0.0.73' is
The likely response is the same as for the HNAME request
HOST : 10.0.0.73 : SRI-NIC,NIC : FOONLY-F3 : TENEX : NCP :
3. ALL Query - Deliver the entire internet host table in
machine-readable form. For example
ALL ;where is a carriage return/
The likely response is the keyword 'BEGIN' followed by
colon ':', followed by the entire internet host table
the format specified in RFC 810, followed by 'END:'.
example
BEGIN
NET : 10.0.0.0 : ARPANET :
NET : 18.0.0.0 : LCSNET :
GATEWAY : 10.0.0.77, 18.8.0.4 : MIT-GW :: MOS : IP/GW :
HOST : 10.0.0.73 : SRI-NIC,NIC : TENEX : FOONLY-F
NCP/TELNET, NCP/FTP, TCP :
HOST : 10.2.0.11 : SU-TIP, FELT-TIP ::
END
ERROR
1. ERR Reply - may occur on any query, and should be
any access program using the name server. Errors are
the
ERR : : :
as
ERR : NAMNFD : Name not found :
[Page 3]
1 March 1982
RFC 811 Hostnames
The error code is a unique descriptor, limited to 8
in length for any given error. It may be used by the
program to identify the error and, in some cases, to handle
automatically. The string is an accompanying message for
given error for that case where the access program simply
the error message. Current codes and their
interpretations
NAMNFD -- Name not found; name not in
ADRNFD -- Address not found; address not
ILLCOM -- Illegal command; command key
TMPSYS -- Temporary system failure, try
The host name server described above runs over a single
internet host name/address data base. This data base is
extension of the old ARPANET Hosts.txt file, and is
maintained by the NIC to provide continuity during
transition and expansion to the internet environment. We
the central administration of a global host name data base
along with this simple name server, as an interim solution
the way to a decentralized, distributed name/
translation service. The NIC welcomes your comments
suggestions for such an expanded service. Send comments
NIC@SRI-NIC
1. Feinler, E., Harrenstien, K., Su, Z. and White, V
DoD Internet Host Table Specification, RFC 810,
Information Center, SRI International, March 1, 1982.
2. Postel, J. Address Mappings, RFC 796, Information
Inst., Univ. of Southern Calif., Marina Del Rey, Sept
1981.
3. Pickens, J., Feinler, E., and Mathis, J. The NIC
Server
A Datagram-based Information Utility, Network
Center, SRI International, July 1979.
[Page 4]
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
