Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

You can copy and modify the sample files provided:
PurposeFile
Sample of /etc/named.conf provided for the nonsecure
version of named.
/etc/dns923/named.conf
Sample of /etc/named.conf provided for the secure
version of named.
/etc/dns_secure/ named.conf
Sample of /etc/rndc.conf provided for the nonsecure
version of rndc.
/etc/dns923/rndc.conf
Sample of /etc/rndc.conf provided for the secure
version of rndc.
/etc/dns_secure/ rndc.conf
See the named(8), lwresd(8), rndc(8), and nsupdate(8) reference pages online or the
DNS Configuration and Management Manual for more information about the use of these files
with the nonsecure BIND 9 server. See the dnssec_named(8), lwresd(8), dnssec_rndc(8),
and dnssec_nsupdate(8) reference pages online or the DNS Configuration and Management
Manual for more information about the use of these files with the secure BIND 9 server.
The DNS security extension utilities (dnssec-keygen and dnssec-signzone) generate the
following additional files:
PurposeFile
Public key for a signed zone. This file is created by
dnssec-keygen.
.keybasename
Private key for a signed zone. This file is created by
dnssec-keygen.
.privatebasename
Signed zone file. This file is created by
dnssec-signzone.
.signedzone-filename
See the BIND 9 Administrator Reference Manual and the DNS Configuration and Management
Manual for more information about these files.
Adding a Server
Some kinds of OSS servers can be added to the OSS configuration database. In the current RVU,
you can add only an OSS name server for a fileset other than the root fileset.
To add an OSS name server to the OSS configuration database:
1. Determine the appropriate configuration for the new server. For help in defining an appropriate
configuration, see the rules described under “The ZOSSSERV File” (page 107).
2. Use the SCF ADD SERVER command to add the new server to the configuration database.
3. If the new OSS name server is assuming some of the workload of an existing OSS name
server:
a. Use the ALTER FILESET command to change the OSS name server assigned to the
NAMESERVER attribute of a started fileset.
b. Use the STOP FILESET command to stop the started fileset.
4. Use the START FILESET command to start (mount) the new or stopped fileset assigned to the
new OSS name server. This action automatically starts the new OSS name server.
5. If your site uses the STARTOSS utility and the new OSS name server services a new fileset,
you should also add the new fileset name to the OSSINFIL file. See “OSSINFIL File” (page 408)
for more information.
120 Managing Servers