Technical data

Configuring and Managing BIND
5.6 Configuring BIND with SET CONFIGURATION Commands
5.6.1 Setting Up a Master Name Server
To instruct the master name server to read the appropriate database files
using the information in TCPIP$CONFIGURATION.DAT, use the SET
CONFIGURATION BIND command. Use the SHOW CONFIGURATION
BIND command to display BIND information from the configuration database
(TCPIP$CONFIGURATION.DAT).
The following commands tell the name server to read the appropriate files:
Example 5–9 Reading Database Files
TCPIP> SET CONFIGURATION BIND /CACHE
TCPIP> SET CONFIGURATION BIND -
_TCPIP> /PRIMARY=(DOMAIN:0.0.127.IN-ADDR.ARPA, FILE:NAMED.LOCAL)
TCPIP> SET CONFIGURATION BIND -
_TCPIP> /PRIMARY=(DOMAIN:UCX.ERN.SEA.COM, FILE:UCX_ERN_SEA_COM.DB)
TCPIP> SET CONFIGURATION BIND -
_TCPIP> /PRIMARY=(DOMAIN:208.20.9.IN-ADDR.ARPA, FILE:208_20_9_IN-ADDR_ARPA.DB)
To view these settings, use the SHOW CONFIGURATION BIND command.
5.6.2 Setting Up a Secondary (Slave) Name Server
Configure a secondary server to populate itself by copying the DNS database files
from the master server.
To configure a secondary server, enter the following commands:
TCPIP> SET CONFIGURATION BIND /CACHE
TCPIP> SET CONFIGURATION BIND -
_TCPIP> /PRIMARY=(DOMAIN:0.0.127.IN-ADDR.ARPA, FILE:NAMED.LOCAL)
TCPIP> SET CONFIGURATION BIND -
_TCPIP> /SECONDARY=(DOMAIN:UCX.ERN.SEA.COM, -
_TCPIP> FILE:UCX_ERN_SEA_COM.DB, -
_TCPIP> HOST:OWL)
TCPIP> SET CONFIGURATION BIND -
_TCPIP> /SECONDARY=(DOMAIN:208.20.9.IN-ADDR.ARPA, -
_TCPIP> FILE:208_20_9_IN-ADDR_ARPA.DB, -
_TCPIP> HOST:OWL.UCX.ERN.SEA.COM))
5.6.3 Setting Up a Cache-Only Server
To configure a cache-only server, enter:
TCPIP> SET CONFIGURATION BIND /CACHE
This command points the server to the file NAMED.CA.
5.6.4 Setting Up a Forwarder Name Server
To configure a forwarder, enter the following command:
TCPIP> SET CONFIGURATION BIND /FORWARDERS=(HOST:host)
5–32 Configuring and Managing BIND