 |
Index for
Section 8 |
|
 |
Alphabetical
listing for B |
|
 |
Bottom of
page |
|
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 master, slave, caching-
only, forward-only, or stub server, but not as a client.
You can configure DNS/BIND by executing the following command, which
invokes a graphical user interface:
# /usr/sbin/sysman dns_server
Alternatively, on a character-cell terminal, you can use the following
command to invoke a command-line interface:
# /usr/sbin/sysman -ui cui dns_server
To exit the script without configuring BIND, hit the return key and choose
e from the list of options. See sysman(8) for more information about the
SysMan Menu.
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.common 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.
Also, it asks you if you want to add localhost to the access control list.
This gives users already logged on to this system permission to display on
this 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 master, slave, caching-
only, stub, or forward-only server.
If you are setting up your system as a slave, forward-only, or stub server,
you must know the name of the host that is serving as the master server.
If you specify the fully qualified name of the server, you must include a
trailing dot (.). For more information, see the Network Administration
guide.
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 Master Server
The master server runs the named daemon and contains the master copy of the
hosts database. Use the following procedure to set up the master 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 master 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 master 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 as previously described. An explanation
of bindsetup is displayed.
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 m 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 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 Slave Server
Slave servers run the named daemon and provide backup for the master
server. Periodically, when the master server indicates that the database
files have been updated, the slave server updates its copy of the files
from the master server. Use the following procedure to set up a slave
server:
1. Invoke the bindsetup script as previously described. An explanation
of bindsetup is displayed.
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 master server for your domain.
5. Enter the host name then the IP address of the master 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-Only Server
Caching-only 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-
only server:
1. Invoke the bindsetup script as previously described. An explanation
of bindsetup is displayed.
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. 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 Forward-only Server
Forward-only servers run the named daemon and forward queries to the list
of forwarders specified in their configuration file. Forward-only servers
forward queries until the list is exhausted or the query is satisfied.
They store the information they receive until the data expires. Use the
following procedure to set up a forward-only server:
1. Invoke the bindsetup script as previously described. An explanation
of bindsetup is displayed.
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 f 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 the 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 Stub Server
A stub server is a master server that delegates authority for a specified
subzone to a server local to the subzone. It is implemented to allow the
administrator for a given subzone to change the configuration of the
subzone without affecting the configuration file on the master server. Use
the following procedure to set up a stub server. Run the bindsetup script
on the server that will have authority for the subzone, not on the master
server:
1. Invoke the bindsetup script as previously described. An explanation
of bindsetup is displayed.
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 t option from the Configuration Menu, and enter c after
bindsetup explains that you must know the name and IP address of the
BIND master server for your domain.
5. Enter the host name then the IP address of the master 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.
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.conf
BIND server configuration (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 master server hosts file.
/etc/namedb/hosts.rev
BIND master server reverse address hosts file.
/etc/resolv.conf
BIND data file.
SEE ALSO
Commands: named(8), nslookup(8), svcsetup(8), sysman(8)
Files: named.conf(4), resolv.conf(4), svc.conf(4)
Network Services: bind_intro(7)
Network Administration
|
Index for
Section 8 |
|
|
Alphabetical
listing for B |
|
 |
Top of
page |
|