Technical data

Configuring and Managing BIND
5.3 Configuring the BIND Server (BIND 8.1)
3. Run the SYS$COMMON:[SYSMGR]TCPIP$BIND_CLUSTER_SETUP.COM
command procedure.
This procedure creates two other command procedures that manage the
startup and shutdown processes of the BIND component in a cluster
environment:
• SYS$COMMON:[SYSMGR]TCPIP$BIND_COMMON_STARTUP.COM
• SYS$COMMON:[SYSMGR]TCPIP$BIND_COMMON_SHUTDOWN.COM
These files define the BIND system logicals and accounting information. To
remove the failover setup from your system, delete these two files.
4. Place any database files to be shared in the common directory.
Note
Be careful to remove from SYS$SPECIFIC:[BIND] any databases that
are to be shared. Using the search list logical, BIND will find any
SYS$SPECIFIC:[BIND] databases first and use those. This may not be
the result you want.
5. Start up BIND by entering the following command:
$ @SYS$COMMON:[SYSMGR]TCPIP$BIND_STARTUP.COM
Caution
The use of dynamic updates in conjunction with a master BIND server
participating in cluster failover and redundancy is not supported and may
cause serious problems.
5.3.7.1 Changing the BIND Database
If multiple master BIND servers are running in a cluster, and a change is made
to the common BIND database, the database must be reloaded on each node
running the master BIND server. To reload the BIND database on every node
in the cluster where the master BIND server is running, enter the following
command:
TCPIP> SET NAME_SERVICE /INITIALIZE /CLUSTER=dev:[directory]
The /CLUSTER qualifier takes the directory specification of the common BIND
directory as a value. If you omit the device and directory, it defaults to:
common_device:[TCPIP$BIND_COMMON]
In this case, common_device is automatically generated in the following manner:
• If the SYSUAF logical is defined, the the common disk is determined from its
definition.
• If SYSUAF logical is not defined, the system uses SYS$SYSDEVICE as the
default device.
5–24 Configuring and Managing BIND