Hostnames Server (RFC0811)
Original Publication Date: 1982-Mar-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
K. Harrenstien: AUTHOR [+2]
More keywords will be added as new needs are recognized. A more detailed description of the allowed requests/responses will follow.
Ken Harrenstien RFC-811
Vic White 1 March 1982
Network Information Center
The NIC Internet Hostnames Server is an NCP/TCP-based host
information program and protocol running on the SRI-NIC
machine. It is one of a series of ARPANET/Internet name
services maintained by the Network Information Center (NIC) at
SRI International on behalf of the Defense Communications
Agency (DCA). The function of this particular server is to
deliver machine-readable name/address information describing
networks, gateways, hosts, and eventually domains, within the
internet environment. As currently implemented, the server
provides the information outlined in the DoD Internet Host
Table Specification (RFC 810).
The name server accepts simple text query requests of the form
where square brackets ("") indicate an optional field. The
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 form
response, and the rest of the response is interpreted in the
context of the key.
The currently defined keywords are:
HNAME (find entry with given name)
HADDR (find entry with given address)
ALL (return entire host table)
1 March 1982
RFC 811 Hostnames Server
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. A
more detailed description of the allowed requests/responses
To access this server from a program, connect to service host
TCP: port 101 decimal
NCP: socket 101 decimal for ICP
send the information query, and await the response.
Note: Care should be taken to interpret the nature of the
reply (e.g, single record or multiple record), so th...