Technical data

Configuring and Managing BIND
5.1 Key Concepts
If you configure a forwarder server, you must provide the name of the host to
which requests outside your zones of authority are forwarded.
5.2 Migrating to BIND 8.1
If you set up your BIND environment using a previous version of the
TCP/IP Services product, you must convert the UCX databases and configuration
information to the new BIND 8.1 format.
To convert your BIND configuration, enter the following command:
TCPIP> CONVERT/CONFIGURATION BIND
This command extracts the BIND-specific configuration information from
UCX$CONFIGURATION.DAT and creates the BIND 8.1 configuration file
TCPIP$BIND.CONF. It renames your BIND databases, where necessary (see
Section 5.2.1 for more information).
You can continue to use the SET CONFIGURATION BIND commands to make
changes to your configuration (see Section 5.6), or you can make changes by
editing the text file TCPIP$BIND.CONF (see Section 5.3). If you continue to
use the SET CONFIGURATION BIND commands, you must also enter the
CONVERT/CONFIGURATION BIND command in order for your changes to take
effect.
5.2.1 Navigating Two Different BIND Environments
This section summarizes the differences between the UCX BIND implementation
and BIND 8.1.
It is important to remember that in BIND 8.1, name servers are configured by
editing a text configuration file. The use of this file is described in Section 5.3.
Compaq recommends, but does not require, that you use the configuration file
to set up BIND. You can continue using the TCPIP$CONFIG and the SET
CONFIGURATION BIND commands to set up your BIND environment as you
did with previous releases of this product. The term UCX BIND in Table 5–1
describes the previous configuration method even though this method is still valid
in the current release.
Table 5–1 describes changes to the database and configuration file names.
Table 5–1 UCX BIND and BIND 8.1 Differences
Database/File Names UCX BIND BIND 8.1
Configuration information UCX$CONFIGURATION.DAT TCPIP$BIND.CONF
Local loopback files NAMED.LOCAL LOCALHOST.DB,
127_0_0.DB
Forward lookup file domain_name.DB domain_name.DB
Reverse lookup file address.DB address.DB
Cache file NAMED.CA ROOT.HINT
5–4 Configuring and Managing BIND