file.lst

早期freebsd实现

         responses  using  topology  information  that  only
         exists on the client's host.


      66..11..1100..  BBoogguuss NNaammee SSeerrvveerrss

              It happens occasionally that some remote  name
         server goes ``bad''.  You can tell your name server
         to refuse to listen to or ask questions of  certain
         other  name  servers  by  listing them in a _b_o_g_u_s_n_s
         directive in your _n_a_m_e_d_._b_o_o_t file.  Its  syntax  is
         the  same  as _f_o_r_w_a_r_d_e_r_s -- you just give it a list
         of dotted-quad Internet addresses.

              Note that _b_o_g_u_s_n_s support  is  a  compile-time
         option  which your vendor may not have enabled when
         they built your operating system.














NNaammee SSeerrvveerr OOppeerraattiioonnss GGuuiiddee ffoorr BBIINNDD              SSMMMM::1100--1155


      66..11..1111..  SSeeggmmeenntteedd BBoooott FFiilleess

              If you are secondary for a lot of  zones,  you
         may  find  it  convenient  to split your _n_a_m_e_d_._b_o_o_t
         file  into  a  static  portion  which  hardly  ever
         changes  (directives  such  as _d_i_r_e_c_t_o_r_y, _s_o_r_t_l_i_s_t,
         _x_f_r_n_e_t_s and _c_a_c_h_e could go here), and dynamic  por-
         tions  that  change frequently (all of your _p_r_i_m_a_r_y
         directives might go in one file, and  all  of  your
         _s_e_c_o_n_d_a_r_y  directives  might  go in another file --
         and either or both of these might be fetched  auto-
         matically  from  some  neighbor  so  that  they can
         change your list of secondary zones without requir-
         ing  your active intervention).  You can accomplish
         this via the _i_n_c_l_u_d_e directive, which takes just  a
         single  file  name  as its argument.  No quotes are
         needed around the file name.  The file name will be
         evaluated  after  the  name  server has changed its
         working directory to that specified in  the  _d_i_r_e_c_-
         _t_o_r_y  directive,  so you can use relative pathnames
         if your system supports them.

   66..22..  RReessoollvveerr CCoonnffiigguurraattiioonn

           The resolver will try to contact a nameserver  on
      the  localhost  if  it  cannot  find its configuration
      file.  You should install the  configuration  file  on
      every host anyway, since you can list the local host's
      address if the localhost runs a nameserver, and  there
      is  no other recommended way to specify a system-level
      default domain.  Note that if you  wish  to  list  the
      local  host  in  your resolver configuration file, you
      should  probably  use  its  primary  Internet  address
      rather  than  a  localhost  alias such as 127.0.0.1 or
      0.0.0.0.  This is due to a bug in the handling of con-
      nected  SOCK_DGRAM sockets in some versions of the BSD
      networking code.  If you must  use  an  address-alias,
      you  should  prefer  0.0.0.0  (or  simply  ``0'') over
      127.0.0.1, though be warned that depending on the vin-
      tage of your BSD-derived networking code, both of them
      are capable of failing in their own ways.

           The     configuration     file's     name      is
      _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f.    This  file  designates  the  name
      servers on the network that should  be  sent  queries.
      It  is  considered reasonable to create this file even
      if you run a local server, since its contents will  be
      cached by each client of the resolver library when the
      client makes its first call to a resolver routine.  If
      you  run  a  name  server  locally,  list  it  in your
      _r_e_s_o_l_v_._c_o_n_f file.












SSMMMM::1100--1166              NNaammee SSeerrvveerr OOppeerraattiioonnss GGuuiiddee ffoorr BBIINNDD


           The _r_e_s_o_l_v_._c_o_n_f file contains directives, one per
      line, of the following forms:

          ; comment
          # another comment
          domain _l_o_c_a_l_-_d_o_m_a_i_n
          search _s_e_a_r_c_h_-_l_i_s_t
          nameserver _s_e_r_v_e_r_-_a_d_d_r_e_s_s
          sortlist _s_o_r_t_-_l_i_s_t

      The  _d_o_m_a_i_n  and  _s_e_a_r_c_h  directives  should  be given
      exactly once.  If the _s_e_a_r_c_h directive is  given,  the
      first  item in the given _s_e_a_r_c_h_-_l_i_s_t will override any
      previously-specified  _l_o_c_a_l_-_d_o_m_a_i_n.   The   _n_a_m_e_s_e_r_v_e_r
      directive  may  be given up to three times; additional
      _n_a_m_e_s_e_r_v_e_r directives will be ignored.   Comments  may
      be  given  by  starting  a line with a ``;;'' or ``##'';
      note that comments were not permitted in  versions  of
      the  resolver  earlier than the one included with BIND
      4.9 -- so if your vendor's resolver supports comments,
      you know they are really on the ball.

           The  _l_o_c_a_l_-_d_o_m_a_i_n  will be appended to any query-
      name that does not contain a ``..''.  _l_o_c_a_l_-_d_o_m_a_i_n  can
      be  overridden  on  a per-process basis by setting the
      LOCALDOMAIN environment variable.   Note  that  _l_o_c_a_l_-
      _d_o_m_a_i_n processing can be disabled by setting an option
      in the resolver.

           The _s_e_a_r_c_h_-_l_i_s_t is a list of  domains  which  are
      tried, in order, as qualifying domains for query-names
      which do not contain a ``..''.  Note  that  _s_e_a_r_c_h_-_l_i_s_t
      processing can be disabled by setting an option in the
      resolver.

           The _s_e_r_v_e_r_-_a_d_d_r_e_s_s's are aggregated and then used
      as   the  default  destination  of  queries  generated
      through the resolver.  This is, in  other  words,  the
      way you tell the resolver which name servers it should
      use.  It is possible for a given client application to
      override  this list, and this is often done inside the
      name server (which is itself a _r_e_s_o_l_v_e_r client) and in
      test programs such as _n_s_l_o_o_k_u_p.

           The  _s_o_r_t_-_l_i_s_t  is  a list of IP address, netmask
      pairs. Addresses returned by gethostbyname are  sorted
      tp  the  order  specifed  by this list.  Any addresses
      that do  not  match  the  address  netmask  pair  will
      returned  after those that do. The netmask is optional
      and the natural netmask will be used if not specified.

           Finally,  if the environment variable HOSTALIASES
      is set, it is taken to contain  the  name  of  a  file










NNaammee SSeerrvveerr OOppeerraattiioonnss GGuuiiddee ffoorr BBIINNDD              SSMMMM::1100--1177


      which  in turn contains resolver-level aliases.  These
      aliases are applied only to names which do not contain
      any  ``..''  characters, and they are applied to query-
      names before the query is generated.   Note  that  the
      resolver  options  governing  the  operation of _l_o_c_a_l_-
      _d_o_m_a_i_n and _s_e_a_r_c_h_-_l_i_s_t do not apply to HOSTALIASES.


   66..33..  CCaacchhee IInniittiiaalliizzaattiioonn

      66..33..11..  rroooott..ccaacchhee

              The name server needs to know the servers that
         are  the  authoritative  name  servers for the root
         domain of the network.  To do this we have to prime
         the name server's cache with the addresses of these
         higher authorities.  The location of this  file  is
         specified  in  the  boot  file.  This file uses the
         Standard Resource Record  Format  (aka.  Masterfile
         Format) covered further on in this paper.

      66..33..22..  nnaammeedd..llooccaall

              This  file  specifies  the  _P_T_R record for the
         local loopback interface, better  known  as  _l_o_c_a_l_-
         _h_o_s_t,  whose  network  address  is  127.0.0.1.  The
         location of this file  is  specified  in  the  boot
         file.  It is vitally important to the proper opera-
         tion  of  every  name  server  that  the  127.0.0.1
         address have a _P_T_R record pointing back to the name
         ``llooccaallhhoosstt.._m_y_._d_o_m_._a_i_n''.  The  name  of  this  _P_T_R
         record  is always ``11..00..00..112277..IINN--AADDDDRR..AARRPPAA''.  This
         is neccessary if you want your users to be able  to
         use    hostname-authentication    (_h_o_s_t_s_._e_q_u_i_v   or
         _~_/_._r_h_o_s_t_s) on the name ``llooccaallhhoosstt''.   As  implied
         by  this _P_T_R record, there should be an _A record in
         your    domain     specifying     that     ``llooccaall--
         hhoosstt.._m_y_._d_o_m_._a_i_n''    has   the   Internet   address
         127.0.0.1.


   66..44..  DDoommaaiinn DDaattaa FFiilleess

           There are two standard files for  specifying  the
      data  for  a  domain.   These  are _h_o_s_t_s and _h_o_s_t_._r_e_v.
      These files use the Standard  Resource  Record  Format
      covered later in this paper.  Note that the file names
      are arbitrary; many network administrators  prefer  to
      name  their zone files after the domains they contain,
      especially in the average case which is where a  given
      server  is primary and/or secondary for many different
      zones.











SSMMMM::1100--1188              NNaammee SSeerrvveerr OOppeerraattiioonnss GGuuiiddee ffoorr BBIINNDD


      66..44..11..  hhoossttss

              This file contains  all  the  data  about  the
         machines  in  this zone.  The location of this file
         is specified in the boot file.

      66..44..22..  hhoossttss..rreevv

              This file specifies the  IN-ADDR.ARPA  domain.
         This  is  a  special domain for allowing address to
         name mapping.  As internet host  addresses  do  not
         fall  within domain boundaries, this special domain
         was  formed  to   allow   inverse   mapping.    The
         IN-ADDR.ARPA  domain  has four labels preceding it.
         These labels correspond  to  the  4  octets  of  an
         Internet  address.   All four octets must be speci-
         fied even if  an  octets  is  zero.   The  Internet
         address   128.32.0.4   is  located  in  the  domain
         4.0.32.128.IN-ADDR.ARPA.   This  reversal  of   the
         address is awkward to read but allows for the natu-
         ral grouping of hosts in a network.

   66..55..  SSttaannddaarrdd RReessoouurrccee RReeccoorrdd FFoorrmmaatt

           The records in the name  server  data  files  are
      called resource records.  The Standard Resource Record
      Format (RR) is specified in RFC1035.  The following is
      a general description of these records:

      _{_n_a_m_e_}   _{_t_t_l_}   _a_d_d_r_-_c_l_a_s_s   _R_e_c_o_r_d _T_y_p_e   _R_e_c_o_r_d _S_p_e_c_i_f_i_c _d_a_t_a

      Resource  records  have a standard format shown above.
      The first field is  always  the  name  of  the  domain
      record  and it must always start in column 1.  For all
      RR's other than the first in a file, the name  may  be
      left  blank;  in that case it takes on the name of the
      previous RR.  The second field is an optional time  to
      live field.  This specifies how long this data will be
      stored in the data base.  By leaving this field  blank
      the  default time to live is specified in the _S_t_a_r_t _O_f
      _A_u_t_h_o_r_i_t_y resource  record  (see  below).   The  third
      field  is the address class; currently, only one class
      is supported: _I_N  for  internet  addresses  and  other
      internet information.  Limited support is included for
      the _H_S  class,  which  is  for  MIT/Athena  ``Hesiod''
      information.   The fourth field states the type of the
      resource record.  The fields after that are  dependent
      on the type of the RR.  Case is preserved in names and
      data fields when loaded into  the  name  server.   All
      comparisons  and  lookups in the name server data base
      are case insensitive.












NNaammee SSeerrvveerr OOppeerraattiioonnss GGuuiiddee ffoorr BBIINNDD              SSMMMM::1100--1199


      TThhee ffoolllloowwiinngg cchhaarraacctteerrss hhaavvee ssppeecciiaall mmeeaanniinnggss::