DNS Configuration and Management Manual (G06.25+, H06.03+)

Configuring and Managing DNS 9.2.3
HP DNS Configuration and Management Manual—529432-001
3-2
Stopping the named Process as a Persistent
Process
Stopping the named Process as a Persistent Process
1. To stop the named process if it is configured as a persistent process
(autorestart > 0), issue the SCF ABORT command to the NonStop Kernel
subsystem as shown:
For more information about managing persistence, see the SCF Reference Manual for
the Kernel Subsystem in NTL.
Specifying a TCP/IP Process By Using a
Runtime Option
By default, the named process binds to the TCP/IP process $ztc0. To make the named
process use the TCP/IP process that is specified at runtime, a runtime option (-T) is
provided (the -T option takes the name of the TCP/IP process that is to be used by
named).
No checking is done by named for the validity of the process name. If you specify an
invalid TCP/IP process name, the named process will not start.
If you do not specify the -T option, named gets bound to $ztc0.
To run named on the TCP/IP process $ztcp2, issue the following command:
Using the named-bootconf Utility to Migrate
the Configuration File
The DNS configuration-file syntax has changed significantly from the Version 4.x to the
Version 9.x. The DNS 4.x configuration file can be converted to a DNS 9.x
configuration file by running the script named-bootconf.sh. This shell script takes the
old configuration file as input and produces the new syntax as output, which can then
be redirected to a file.
In the following example, the name of the old configuration file (DNS 4.x format) is
named.boot, and the name of the new generated file (DNS 9.x format) is named.conf.
->abort $zzkrn.#named
/etc/dns923> named -T \$ztcp2
Example 3-1. Migrating the Configuration File
/etc/dns923> named-bootconf.sh < named.boot > named.conf