Configuring Domain Name System (DNS) servers

Configuring a DNS name server

Configuring a DNS name server consists of setting up /etc/inet/named.conf and other files. UnixWare provides the DNS Manager as a convenient way of setting up and maintaining these files for master, slave, and stub name servers, or for servers that provide a mixture of these services.

WARNING: For correct operation of the DNS Manager and other SCOadmin managers on a host that you are configuring remotely, there must be an entry for the localhost address (127.0.0.1) in the /etc/hosts file on the remote host.

See ``The Client Manager interface'' for instructions on how to configure a name service client using the Client Manager.

If you choose not to use the DNS Manager or the Client Manager, you must edit the configuration files yourself:

If you are enabling a slave, stub, or caching-only server, the minimum configuration is to set up named.conf(4tcp), named.local(4tcp), and root.cache(4tcp) files. For a slave or stub server, you should also configure a backup file that will be used to hold transferred zone data. In the case of a stub server, only a limited number of records are transferred and stored.
To configure a server which is master for at least one zone, the suggested configuration is to set up named.conf(4tcp), named.local(4tcp), and root.cache(4tcp) files plus a pair of suitably named named.hosts(4tcp), and named.rev(4tcp) files for each zone. Additionally, you can configure a single named.soa(4tcp) file that defines one SOA (Start of Authority) record to be included by all the zone named.hosts and named.rev files, or you can configure an individual SOA record for each zone.
To configure the use of name service by client software, edit the resolv.conf(4tcp) file.