Configuring the Domain Name Service

Configuring a secondary server

  1. Copy /etc/named.d/named.conf.sec to /etc/named.conf.

  2. Edit /etc/named.conf to contain the zones for which the server is secondary, including zone names, file locations, and the IP address of the primary server.

  3. If needed, edit /etc/named.conf to contain the IP address of one or more forwarders.

  4. If needed, edit /etc/named.conf to add the slave directive.

  5. Start the DNS daemon, named, from the command line by running the following commands:

    /etc/ndc stop (to stop the server)
    /etc/ndc start (to restart the server)

    Once configured, named starts and stops automatically as the system moves in and out of multiuser mode.

  6. Test DNS by using nslookup to look up a remote name.

The following is an example configuration file for a secondary server:
   // generated by
   // @(#) named.conf.sec 108.1 02/06/19

options { directory "/etc/named.d"; forward only; forwarders {;; }; /* * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * directive below. Previous versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; };

// // NOTE: If you are running as a secondary Name Server, old copies (if they // exist) of the files {directory}/named.hosts and {directory}/named.rev // should be removed before starting named.

zone "" { type slave; file "named.hosts"; masters {;;; }; };

zone "." { type hint; file "root.cache"; };

zone "" { type slave; file "named.rev"; masters {;;; }; };

zone "" { type master; file "named.local"; };

See also:

Next topic: Configuring a remote server
Previous topic: Configuring a primary server

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003