 |
Index for Section 8 |
|
 |
Alphabetical listing for B |
|
bindsetup(8)
NAME
bindsetup - Sets up the Berkeley Internet Name Domain (BIND) service
SYNOPSIS
/usr/sbin/bindsetup
DESCRIPTION
The bindsetup command sets up the Berkeley Internet Name Domain (BIND)
service on your system and places hosts 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.
In order to run BIND, 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.
When you are using the bindsetup command to configure BIND on your system
for the first time, it edits the /etc/hosts and /etc/rc.config files and
changes the local host name to the BIND host name.
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.
If you are setting up your system as a client or a secondary or a slave
server, you must know the name of the host that is serving as either the
primary or secondary server. If you specify the fully qualified name of the
server, you must include a trailing dot (.). For more information, see the
guide to Network Administration.
You should run the bindsetup command as superuser and with the system in
multiuser mode.
When you run bindsetup, 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 is installed on a system, it cannot be used until the
/etc/svc.conf file is modified to indicate that BIND is being used to serve
hosts information. The bindsetup command allows you to edit the
/etc/svc.conf file by giving you the option of calling the
/usr/sbin/svcsetup script from within it. If you do not edit the
/etc/svc.conf file from within bindsetup, you must edit it by invoking the
svcsetup script from the command line, or manually.
Setting Up the Primary Server
The primary server runs the named daemon and contains the master copy of
the hosts database. Use the following procedure to set up the primary
server:
1. Copy into the /etc/namedb/src directory the hosts file that you want
to convert to the BIND hosts database.
To create the source file from which the hosts database will be
created, update the primary server's local /etc/hosts file and then
copy it into the /etc/namedb/src directory. Note that if a system,
host1 for example, is in your BIND domain and is running BIND but is
not included in the primary server's hosts database, other systems in
the domain cannot obtain host1's IP address. See hosts(4) for
information.
Note that the file that you copy into the /etc/namedb/src directory
must be named hosts.
2. Invoke the bindsetup script.
3. Press Return and choose the a option from the Action Menu.
4. Enter c to continue after the script tells you that you must know your
default domain name or exit, and then enter your domain name.
5. Choose the p option from the Configuration Menu, and answer yes when
bindsetup asks if you want to convert the source files in
/etc/namedb/src to the appropriate BIND format.
The bindsetup script indicates which system files it is updating and
sets the host name to the fully qualified BIND host name.
6. Indicate whether you want bindsetup to start the named daemon. If you
answer yes, bindsetup starts the daemon. If you answer no, use the
following command to start the daemon manually after bindsetup exits
and the system prompt (#) is displayed:
# /sbin/init.d/named start
7. Indicate the order in which to resolve host name queries. This step
enables you to choose the order in which to resolve host name queries,
as follows:
·
Check the local /etc/hosts database before querying BIND (choose
option 1). This is the recommended order.
·
Query BIND first (choose option 2).
·
Run the svcsetup script to customize service order selection (choose
option 3).
If you choose option 3, the bindsetup script invokes the svcsetup
script, which allows you to modify the database services selection
file (the svc.conf file). See svcsetup(8) and svc.conf(4) for more
information.
Setting Up a Secondary Server
Secondary servers run the named daemon and provide backup for the primary
server. Secondary servers load their database files from the primary server
and periodically poll the primary server to ensure that their databases are
up to date. Use the following procedure to set up a secondary server:
1. Invoke the bindsetup script. An explanation of bindsetup is displayed
on your screen.
2. Press Return and choose the a option from the Action Menu.
3. Enter c to continue after the script tells you that you must know your
default domain name or exit, and then enter your domain name.
4. Choose the s option from the Configuration Menu, and enter c after
bindsetup explains that you must know the name and IP address of the
BIND primary server for your domain.
5. Enter the host name then the IP address of the primary server for your
domain. If you enter the fully qualified host name, you must include
a trailing dot (.). For example, if the fully qualified host name is
cxcxcx.abc.xyz.com, you would enter it as follows:
cxcxcx.abc.xyz.com.
The bindsetup script indicates which system files it is updating and
sets the host name to the fully qualified BIND host name.
6. Indicate whether you want bindsetup to start the named daemon. If you
answer yes, bindsetup starts the daemon. If you answer no, use the
following command to start the daemon manually after bindsetup exits
and the system prompt (#) is displayed:
# /sbin/init.d/named start
7. Indicate the order in which to resolve host name queries. This step
enables you to choose the order in which to resolve host name queries,
as follows:
·
Check the local /etc/hosts database before querying BIND (choose
option 1). This is the recommended order.
·
Query BIND first (choose option 2).
·
Run the svcsetup script to customize service order selection (choose
option 3).
If you choose option 3, the bindsetup script invokes the svcsetup
script, which allows you to modify the database services selection
file (the svc.conf file). See svcsetup(8) and svc.conf(4) for more
information.
Setting Up a Caching Server
Caching servers run the named daemon and service queries by asking other
servers for the information. They store the information they receive until
the data expires. Use the following procedure to set up a caching server:
1. Invoke the bindsetup script. An explanation of bindsetup is displayed
on your screen.
2. Press Return and choose the a option from the Action Menu.
3. Enter c after the script tells you that you must know your default
domain name or exit, and then enter your domain name.
4. Choose the a option from the Configuration Menu. The bindsetup script
indicates which system files it is updating and sets the host name to
the fully qualified BIND host name.
5. Indicate whether you want bindsetup to start the named daemon. If you
answer yes, the bindsetup script starts the daemon. If you answer no,
use the following command to start the daemon manually after the
bindsetup script exits and the system prompt (#) is displayed:
# /sbin/init.d/named start
6. Indicate the order in which to resolve host name queries. This step
enables you to choose the order in which to resolve host name queries,
as follows:
·
Check the local /etc/hosts database before querying BIND (choose
option 1). This is the recommended order.
·
Query BIND first (choose option 2).
·
Run the svcsetup script to customize service order selection (choose
option 3).
If you choose option 3, the bindsetup script invokes the svcsetup
script, which allows you to modify the database services selection
file (the svc.conf) file). See svcsetup(8) for more information.
Setting Up a Slave Server
Slave servers run the named daemon and forward queries to the list of
forwarders specified in their boot file. Slave servers forward queries
until the list is exhausted or the query is satisfied. Slave servers store
the information they receive until the data expires. Use the following
procedure to set up a slave server:
1. Invoke the bindsetup script. An explanation of bindsetup is displayed
on your screen.
2. Press Return and choose the a option from the Action Menu.
3. Enter c after the script tells you that you must know your default
domain name or exit, and then enter your domain name.
4. Choose option l from the Configuration Menu, and enter c after the
script explains that you must know the names and IP addresses of the
specified BIND servers for your domain.
5. Enter three host names and IP addresses of BIND servers for your
domain. If the host names and IP addresses are not listed in the
/etc/hosts file, the bindsetup script gives you the option of adding
them.
If you enter the fully qualified host name, you must include a
trailing dot (.). For example, if the fully qualified host name is
cxcxcx.abc.xyz.com, you would enter it as follows:
cxcxcx.abc.xyz.com.
6. Indicate that you are finished entering BIND servers. The bindsetup
script indicates which system files it is updating and sets the host
name to the fully qualified BIND host name.
7. Indicate whether you want bindsetup to start the named daemon. If you
answer yes, bindsetup starts the daemon. If you answer no, you must
start the daemon manually after bindsetup exits and the system prompt
(#) is displayed:
# /sbin/init.d/named start
8. Indicate the order in which to resolve host name queries. This step
enables you to choose the order in which to resolve host name queries,
as follows:
·
Check the local /etc/hosts database before querying BIND (choose
option 1). This is the recommended order.
·
Query BIND first (choose option 2).
·
Run the svcsetup script to customize service order selection (choose
option 3).
If you choose option 3, the bindsetup script invokes the svcsetup
script, which allows you to modify the database services selection
file (the svc.conf file). See svcsetup(8) for more information.
Setting Up a Client
BIND clients query servers for host name and address information. They do
not run the named daemon. Use the following procedure to set up a client
system:
1. Invoke the bindsetup script. An explanation of bindsetup is displayed
on your screen.
2. Press Return and choose the a option from the Action Menu.
3. Enter c after the script tells you that you must know your default
domain name or exit, and then enter your domain name.
4. Choose the c option from the Configuration Menu, and enter c after the
script explains that there must be at least one BIND primary or
secondary server configured for your domain and that you must know the
names and IP addresses of the specified BIND servers for your domain.
5. Enter three host names and IP addresses of BIND servers for your
domain. The addresses are placed in the /etc/resolv.conf file, where
the resolver uses them to determine the IP addresses of name servers
it should query. If the host names and IP addresses are not listed in
the /etc/hosts file, the bindsetup script gives you the option of
adding them.
If you enter the fully qualified host name, you must include a
trailing dot (.). For example, if the fully qualified host name is
cxcxcx.abc.xyz.com, you would enter it as follows:
cxcxcx.abc.xyz.com.
6. Indicate that you are finished entering BIND servers. The bindsetup
script indicates which system files it is updating and sets the host
name to the fully qualified BIND host name.
7. Indicate the order in which to resolve host name queries. This step
enables you to choose the order in which to resolve host name queries,
as follows:
·
Check the local /etc/hosts database before querying BIND (choose
option 1). This is the recommended order.
·
Query BIND first (choose option 2).
·
Run the svcsetup script to customize service order selection (choose
option 3).
If you choose option 3, the bindsetup script invokes the svcsetup
script, which allows you to modify the database services selection
file (the svc.conf file). See svcsetup(8) for more information.
FILES
/etc/hosts List of locally maintained host names and IP addresses.
/etc/svc.conf
Database name with the selected naming services.
Default BIND files:
/etc/namedb
BIND server data file directory.
/etc/namedb/named.boot
BIND server boot file.
/etc/namedb/named.ca
BIND server cache file.
/etc/namedb/named.local
BIND server local host reverse address host file.
/etc/namedb/hosts.db
BIND primary server hosts file.
/etc/namedb/hosts.rev
BIND primary server reverse address hosts file.
/etc/resolv.conf
BIND data file.
RELATED INFORMATION
Commands: named(8), nslookup(8), svcsetup(8)
Files: resolv.conf(4), svc.conf(4)
Network Services: bind_intro(7)
Network Administration