NAME

bindsetup - set up the Berkeley Internet Name Domain (BIND) service

SYNTAX

/usr/etc/bindsetup [ −c [ directory ] binddomain IP# ... ]

DESCRIPTION

The bindsetup command sets up the Berkeley Internet Name Domain (BIND) service on your system and places host name and address resolution under BIND control. You can use this command to set up your system as a primary, secondary, slave, or caching server, or as a client.

The bindsetup command checks to see if the file /etc/svcorder exists. If it does not, then bindsetup creates the file and adds an entry for the BIND service and another entry for the local service. If the svcorder file already exists but does not contain an entry for BIND, bindsetup gives you this reminder:

Be sure to update the
/etc/svcorder
file to reflect the proper
order in which to access the BIND Service for host
name and address resolution.

If you are running more than one service, you should consider the order in which the services are to be queried. You can edit the /etc/svcorder file to reflect this order after bindsetup completes.

When running BIND, your system acquires a new host name.  The bindsetup command changes the local host name of your system to the BIND host name. The bindsetup command modifies the /etc/hosts and /etc/rc.local files to reflect the modified host name. The BIND host name consists of the local host name plus the BIND domain names, separated by periods. For example, a BIND host name for a system whose local host name is orange is:

orange.col.ecd.com

Before running bindsetup your system must be established on a local area network. In addition, you must know your system’s default BIND domain name and whether your system will be a primary, secondary, slave, or caching server, or a client. There can be multiple primary servers on a domain. Thus, you should always run the bindsetup command as superuser and with the system in multiuser mode so that the BIND service will not be interrupted in the event that a server goes down.

You should run the bindsetup command as superuser and with the system in multiuser mode.

If you use the −c option with the respective arguments, the bindsetup command sets up your system as a BIND client automatically.

If you run the bindsetup command interactively, that is, with no arguments, a menu is displayed giving you a choice of responses. You are then prompted for further information. Before bindsetup exits, it lists the files that have been updated.

If you are setting up your system as a server, you must edit some files manually after bindsetup completes. The bindsetup command tells you which files need modification. The Guide to the BIND Service provides details about how to edit the files. 

After running the bindsetup command, you should reboot the system to be sure that the modifications to any files take immediate effect.

OPTIONS

−cSilently sets up your system as a BIND client according to the following arguments you supply:

directoryThis argument is required if you are setting up a diskless client from the diskless server.  The directory is the full path name of the root directory for your system (a diskless client) on the diskless server.  The following is an example of a root directory for a diskless client named orange: /var/diskless/dlclient0/orange.root.

binddomainThis is the name of the BIND domain on which your system will be a BIND client.  The following is an example of a BIND domain name: cities.us.

IP#This is the IP address of the BIND server on the domain, for example 128.11.22.33. You can specify one or more BIND server IP addresses, separated by a space.

FILES

/etc/hostsList of locally maintained host names and IP addresses

/etc/rc.localStartup commands pertinent to a specific system

/etc/svcorderList of host name and IP address resolution services Default BIND Files:

/etc/named.bootBIND server boot file

/etc/namedbBIND server data file directory

/etc/namedb/named.caBIND server cache file

/etc/namedb/named.hostsBIND server hosts file

/etc/namedb/named.localBIND server local host reverse address host file

/etc/namedb/named.revBIND server reverse address hosts file

/etc/resolv.confBIND client data file

SEE ALSO

hostname(1), nslookup(1), nsquery(1), gethostent(3n), resolver(3), resolver(5), svcorder(5), named(8)
Guide to the BIND Service

Maintenance