4.3BSD-UWisc/man/cat8/named.8

NAMED(8)            UNIX Programmer's Manual             NAMED(8)



NAME
     named - Internet domain name server

SYNOPSIS
     named [ -d _d_e_b_u_g_l_e_v_e_l ] [ -p _p_o_r_t# ] [ _b_o_o_t_f_i_l_e ]

DESCRIPTION
     _N_a_m_e_d is the Internet domain name server (see RFC883 for
     more details).  Without any arguments, _n_a_m_e_d will read the
     default boot file /_e_t_c/_n_a_m_e_d._b_o_o_t, read any initial data and
     listen for queries.

     Options are:

     -d   Print debugging information.  A number after the ``d''
          determines the level of messages printed.

     -p   Use a different port number.  The default is the stan-
          dard port number as listed in /etc/services.

     Any additional argument is taken as the name of the boot
     file.  The boot file contains information about where the
     name server is to get its initial data.  The following is a
     small example:

          ;
          ;    boot file for name server
          ;
          ; type         domain         source file or host
          ;
          domain         berkeley.edu
          primary        berkeley.edu    named.db
          secondary      cc.berkeley.edu 10.2.0.78 128.32.0.10
          cache          .               named.ca

     The first line specifies that ``berkeley.edu'' is the domain
     for which the server is authoritative.  The second line
     states that the file ``named.db'' contains authoritative
     data for the domain ``berkeley.edu''. The file ``named.db''
     contains data in the master file format described in RFC883
     except that all domain names are relative to the origin; in
     this case, ``berkeley.edu'' (see below for a more detailed
     description).  The second line specifies that all authorita-
     tive data under ``cc.berkeley.edu'' is to be transferred
     from the name server at 10.2.0.78.  If the transfer fails it
     will try 128.32.0.10 and continue trying the address, up to
     10, listed on this line.  The secondary copy is also author-
     itative for the specified domain.  The fourth line specifies
     data in ``named.ca'' is to be placed in the cache (i.e.,
     well known data such as locations of root domain servers).
     The file ``named.ca'' is in the same format as ``named.db''.




Printed 12/27/86        15 November 1985                        1






NAMED(8)            UNIX Programmer's Manual             NAMED(8)



     The master file consists of entries of the form:

          $INCLUDE <filename>
          $ORIGIN <domain>
          <domain> <opt_ttl> <opt_class> <type> <resource_record_data>

     where _d_o_m_a_i_n is "." for root, "@" for the current origin, or
     a standard domain name. If _d_o_m_a_i_n is a standard domain name
     that does not end with ``.'', the current origin is appended
     to the domain. Domain names ending with ``.'' are unmodi-
     fied.  The _o_p_t__t_t_l field is an optional integer number for
     the time-to-live field.  It defaults to zero.  The _o_p_t__c_l_a_s_s
     field is the object address type; currently only one type is
     supported, IN, for objects connected to the DARPA Internet.
     The _t_y_p_e field is one of the following tokens; the data
     expected in the _r_e_s_o_u_r_c_e__r_e_c_o_r_d__d_a_t_a field is in
     parentheses.

     A        a host address (dotted quad)

     NS       an authoritative name server (domain)

     MX       a mail exchanger (domain)

     CNAME    the canonical name for an alias (domain)

     SOA      marks the start of a zone of authority (5 numbers
              (see RFC883))

     MB       a mailbox domain name (domain)

     MG       a mail group member (domain)

     MR       a mail rename domain name (domain)

     NULL     a null resource record (no format or data)

     WKS      a well know service description (not implemented
              yet)

     PTR      a domain name pointer (domain)

     HINFO    host information (cpu_type OS_type)

     MINFO    mailbox or mail list information (request_domain
              error_domain)

NOTES
     The following signals have the specified effect when sent to
     the server process using the _k_i_l_l(1) command.

     SIGHUP    Causes server to read named.boot and reload



Printed 12/27/86        15 November 1985                        2






NAMED(8)            UNIX Programmer's Manual             NAMED(8)



               database.

     SIGINT    Dumps current data base and cache to
               /usr/tmp/named_dump.db

     SIGUSR1   Turns on debugging; each SIGUSR1 increments debug
               level.

     SIGUSR2   Turns off debugging completely.

FILES
     /etc/named.boot          name server configuration boot file
     /etc/named.pid           the process id
     /usr/tmp/named.run       debug output
     /usr/tmp/named_dump.db   dump of the name servers database

SEE ALSO
     kill(1), gethostbyname(3N), signal(3c), resolver(3),
     resolver(5), RFC882, RFC883, RFC973, RFC974, _N_a_m_e _S_e_r_v_e_r
     _O_p_e_r_a_t_i_o_n_s _G_u_i_d_e _f_o_r _B_I_N_D



































Printed 12/27/86        15 November 1985                        3