Page 180 - DCAP106_OPERATING_SYSTEM_TOOLS
P. 180

Unit 10: Servers




          Some versions of BIND will come with a /etc/amed.conf file configured to work as a caching   Notes
          nameserver  which  can  be transformed  to an authoritative nameserver  by adding  the correct
          references to your zone files. Please proceed to the next section if this is the case with your version
          of BIND.
          In  additional  cases  the  named.conf  configuration  file  may  be  hard  to  find.  Some  versions  of
          Linux install BIND as a default caching nameserver using a file names /etc/named.caching-
          nameserver.conf for its configuration. In such cases BIND becomes an authoritative nameserver
          when a correctly configured /etc/named.conf file is created.
          Fortunately BIND comes with samples of all the primary files you need. Table 10.3 explains their
          names and purpose in more detail.
                               Table 10.3: The Primary BIND Configuration Files

              File                 Description
              /etc/named.conf      The main configuration file that lists the location of all your domain's
                                   zone files.
              /etc/named.rfc1912.zones   Base configuration file for a caching name server.
              /var/named/named.ca   A list of the 13 root authoritative DNS servers.

          The  first task  is to  make  sure  your  DNS server will listening  of requests on  all  the required
          network interfaces.


                 Example: The options section of named.conf may be configured to listen completely on
          its internal hidden localhost interface with an IP address of 127.0.0.1 as we see in this example.

          # File: /etc/named.conf
          Options {
           Listen-on port 53 {127.0.0.1; };
          };
          If other devices are going to rely on your server for queries, then you’ll need to either modify this
          or add a selected number of IP addresses on your server.

                 Example: In this example, we allow queries on any interface.

          Listen-on port 53 {any ;};

                 Example: In this example, we allow queries on localhost and address 192.168.1.100.
          listen-on port 53 { 127.0.0.1; 192.168.1.100; };
          Always make sure localhost, 127.0.0.1 is included.




              Task  While it is not required, it is a good practice to configure your DNS server’s named.
             conf file to support BIND views.


          Configuring BIND Views in named.conf

          Our sample scenario believes that DNS queries will be coming from the Internet and that the
          zone files will return information related to the external 97.158.253.26 address of the Web server.




                                           LOVELY PROFESSIONAL UNIVERSITY                                   173
   175   176   177   178   179   180   181   182   183   184   185