4.3BSD - /usr/man/cat8/named.0

NAMED(8)                                                              NAMED(8)


NAME
       named - Internet domain name server

SYNOPSIS
       named [ -d debuglevel ] [ -p port# ] [ bootfile ]

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

       Options are:

       -d     Print  debugging  information.   A number after the ‘‘d’’ deter‐
              mines the level of messages printed.

       -p     Use a different port number.  The default is the  standard  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  ‘‘berke‐
       ley.edu’’. The file ‘‘named.db’’ contains data in the master file  for‐
       mat  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  sec‐
       ondary copy is also authoritative 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’’.

       The master file consists of entries of the form:

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

       where domain is "." for root, "@" for the current origin, or a standard
       domain name. If domain is a standard domain name that does not end with
       ‘‘.’’, the current origin is appended to the domain. Domain names  end‐
       ing  with ‘‘.’’ are unmodified.  The opt_ttl field is an optional inte‐
       ger number for the time-to-live  field.   It  defaults  to  zero.   The
       opt_class  field is the object address type; currently only one type is
       supported, IN, for objects connected to the DARPA Internet.   The  type
       field  is  one  of  the  following  tokens;  the  data  expected in the
       resource_record_data 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 kill(1) command.

       SIGHUP    Causes server to read named.boot and reload 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, Name Server Operations Guide for BIND


4th Berkeley Distribution      15 November 1985                       NAMED(8)