PROXY  WHOIS  RQUOTE  TEXTS  SOFT  FOREX  BBOARD
 Music  Philosophy  Code  Literature  Russian

= ROOT|Technical|RFC|rfc0953.txt =

page 1 of 3



Network Working Group                               K. Harrenstien (SRI)
Request for Comments: 953                                 M. Stahl (SRI)
Obsoletes:  RFC 811                                     E. Feinler (SRI)
                                                            October 1985

                            HOSTNAME SERVER


STATUS OF THIS MEMO

   This RFC is the official specification of the Hostname Server
   Protocol.  This edition of the specification includes minor revisions
   to RFC 811 which brings it up to date.  Distribution of this memo is
   unlimited.

INTRODUCTION

   The NIC Internet Hostname Server is a TCP-based host information
   program and protocol running on the SRI-NIC machine.  It is one of a
   series of internet name services maintained by the DDN 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 [See RFC-952].  For a discussion of future developments
   see also RFC-921 concerning the Domain Name System.

PROTOCOL

   To access this server from a program, establish a TCP connection to
   port 101 (decimal) at the service host, SRI-NIC.ARPA (26.0.0.73 or
   10.0.0.51).  Send the information request (a single line), and read
   the resulting response.  The connection is closed by the server upon
   completion of the response, so only one request can be made for each
   connection.

QUERY/RESPONSE FORMAT

   The name server accepts simple text query requests of the form

      <command key> <argument(s)> []

   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 key> : <rest of response>



 


RFC 953                                                     October 1985
Hostname Server


   where <response key> is a keyword indicating the nature of the
   response, and the rest of the response is interpreted in the context
   of the key.

   NOTE:  Care should be taken to interpret the nature of the reply
   (e.g, single record or multiple record), so that no confusion about
   the state of the reply results.  An "ALL" request will likely return
   several hundred or more records of all types, whereas "HNAME" or
   "HADDR" will usually return one HOST record.

COMMAND/RESPONSE KEYS

   The currently defined command keywords are listed below.  NOTE:
   Because the server and the features available will evolve with time,
   the HELP command should be used to obtain the most recent summary of
   implemented features, changes, or new commands.

      Keyword   Response

      HELP      This information.

      VERSION   "VERSION: " where  will be different for
                each version of the host table.

      HNAME 
                One or more matching host table entries.

      HADDR 
                One or more matching host table entries.

      ALL       The entire host table.

      ALL-OLD   The entire host table without domain style names.

      DOMAINS   The entire top-level domain table (domains only).

      ALL-DOM   Both the entire domain table and the host table.

      ALL-INGWAY
=1=

= PAGE 1 = NEXT > |2|3

UP TO ROOT | UP TO DIR

Google
 


E-mail Facebook Google Digg del.icio.us BlinkList Fark Furl Ma.gnolia Netscape NewsVine Reddit Slashdot Spurl StumbleUpon Technorati YahooMyWeb LiveJournal Blogmarks TwitThis Live News2.ru BobrDobr.ru Memori.ru MoeMesto.ru

0.010287 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 CPU)