DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Configuring the Domain Name Service

Configuring a primary server

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

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

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

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

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

  6. Create the database file(s) for the zone.

  7. 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.

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

The following is an example configuration file for a primary server:
   // generated by named-bootconf.pl
   //
   // @(#) named.conf.pri 108.1 02/06/19
   //
   

options { directory "/etc/named.d"; /* * 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; };

zone "test.sco.com" { type master; file "named.hosts"; };

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

zone "64.168.192.in-addr.arpa" { type master; file "named.rev"; };

zone "0.0.127.in-addr.arpa" { type master; file "named.local"; };

See also:


Next topic: Configuring a secondary server
Previous topic: Configuring a caching-only server

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