Name

bindsetup − set up the Berkeley Internet Name Domain (BIND)/Hesiod service

Syntax

/usr/etc/bindsetup [ −c [ −d directory ] −b binddomain  name1,IP1 name2,IP2 ... ]

Description

The bindsetup command sets up the Berkeley Internet Name Domain (BIND)/Hesiod service on your system and places aliases, auth, group, hosts, networks, passwd, protocols, rpc, and services resolution under BIND/Hesiod control. You can use this command to set up your system as a primary, secondary, slave, or caching server, or as a client.

In order to run BIND/Hesiod, your system’s host name must include the BIND domain name.  The BIND host name consists of the local host name plus the BIND domain name, separated by periods.  For example, the BIND host name for a system whose local host name is orange, and whose BIND domain name is col.ecd.com is orange.col.ecd.com.

The bindsetup command edits the /etc/hosts and /etc/rc.local files and changes the local host name to the BIND host name, if it is not there already.

If the bindsetup command changes your system’s host name, you should reboot the system to be sure that the change is propagated throughout the system.

Before you run bindsetup , your system must be established on a local area network. In addition, you must know the BIND domain name for your local area network, and whether your system will be a primary, secondary, slave, or caching server, or a client.

The bindsetup command asks if you want to run a Kerberos authentication server. You must already have set up Kerberos to do do. For more information, see the Guide to Kerberos. 

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/Hesiod client non-interactively.

If you run the bindsetup command 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.

Once BIND/Hesiod is installed on a machine, it cannot be used until the /etc/svc.conf file is modified to contain BIND entries on the desired database lines.  The bindsetup command reminds a user to run /usr/etc/svcsetup or edit the /etc/svc.conf file manually.

Options

−cSets up your system as a BIND/Hesiod client according to the following arguments you supply on the command line:

−d   directoryThis option and argument are 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:

/dlclient0/orange.root

−b   binddomain
This is the name of the BIND domain on which your system will be a BIND client. For example, cities.us is a sample BIND domain name.

name,IPThis is the host name and the IP address of the BIND server on the domain, for example foobar,128.11.22.33. You can specify one or more BIND server by listing more name,IP arguments, each separated by a space. 

Files

/etc/hosts List of locally maintained host names and IP addresses

/etc/rc.local Startup commands pertinent to a specific system

/etc/svc.conf Database name with the selected naming services

/etc/hesiod.conf
Hesiod configuration file

/etc/kerb.conf List of Kerberos servers

Default BIND Files:

/var/dss/namedb BIND server data file directory

/var/dss/namedb/named.boot
BIND server boot file

/var/dss/namedb/named.ca
BIND server cache file

/var/dss/namedb/named.local
BIND server local host reverse address host file

/var/dss/namedb/hosts.db
BIND primary server hosts file

/var/dss/namedb/hosts.rev
BIND primary server reverse address hosts file

/etc/resolv.conf
BIND data file

See Also

nslookup(1), hesiod(3), hesiod.conf(5), svc.conf(5), svcsetup(8), named(8), krb.conf(5), resolv.conf(5)
Guide to the BIND/Hesiod Service
Guide to Kerberos