Content-type: text/html Man page of bind_manual_setup

bind_manual_setup

Section: Environments, Tables, and Troff Macros (7)
Index Return to Main Contents
 

NAME

bind_manual_setup - Describes how to manually set up the Berkeley Internet Name Domain (BIND) service on your network.  

DESCRIPTION

Setting up a BIND domain includes configuring the following: Primary server Secondary servers Caching servers Slave servers Clients  

Setting Up the Primary Server

There can be only one primary server in a BIND domain. Use the following procedure to set up a BIND primary server: Create the /etc/resolv.conf file.

The /etc/resolv.conf file contains the domain name and the Internet Protocol (IP) address for the local host. Format the /etc/resolv.conf file as follows, substituting your domain name for cities.dec.com: # @(#)resolv.conf # # Description: The resolv.conf file lists name-value pairs that # provide information to the BIND resolver. # # Syntax: domain <domainname> # and # nameserver <address> # # Caution: White space entered after the domain name is not # ignored; it is interpreted as part of the domain name. # # domain <domainname> local domain name # nameserver <address> Internet address of a name server # that the resolver should query # domain cities.dec.com nameserver 127.0.0.1 Create the database files by using the following procedure: Copy into or create in the /etc/namedb/src directory a file called hosts. The hosts file should have the following format: 127.0.0.1 localhost 120.105.1.20 host1.cities.dec.com h1 #BIND server 120.105.1.142 host2 h2 120.105.1.1 host3 h3 #BIND server 120.105.1.13 host4 120.105.2.23 host5 h5 The first field is the IP address. The second field is the host name. The third field is for aliases for the host name (optional). The fourth field is comments, delineated by the number sign (#) (optional). Run the make hosts command from within the /etc/namedb directory by entering the following commands: # cd /etc/namedb # make hosts The make hosts command creates the /etc/namedb/hosts.db and /etc/namedb/hosts.rev files. Any host names with a domain name different from that for which you are creating the database are ignored. For example, if you create the hosts database for the domain cities.dec.com and you have a host name fizzle.nac.dec.com in the file, fizzle.nac.dec.com is ignored. Also, the first host name that the make hosts command encounters that has either no domain name or the default domain name becomes the primary name of the machine. All other names are considered aliases, or CNAMES. For example, for the following entry, the make hosts command considers host2 the primary name of the system and h2 an alias: 120.105.1.20 host2 h2 Create the /etc/namedb/named.ca file.
The /etc/namedb/named.ca file must read as follows: ; ; BIND data file for initial cache data for root domain servers. ; . 99999999 IN NS ns.nic.ddn.mil. . 99999999 IN NS ns.nasa.gov. . 99999999 IN NS terp.umd.edu. . 99999999 IN NS a.isi.edu. . 99999999 IN NS aos.brl.mil. . 99999999 IN NS gunter-adam.af.mil. . 99999999 IN NS c.nyser.net. ns.nic.ddn.mil. 99999999 IN A 192.67.67.53 ns.nasa.gov. 99999999 IN A 128.102.16.10 ; BIND
                99999999       IN    A     192.52.195.10 a.is.edu. 99999999 IN A 26.3.0.103
                99999999       IN    A     128.9.0.107 aos.brl.mil. 99999999 IN A 128.20.1.2 ; BIND
                99999999       IN    A     192.5.25.82 gunter-adam.af.mil. 99999999 IN A 26.1.0.13 c.nyser.net. 99999999 IN A 192.33.4.12 ; BIND terp.umd.edu. 99999999 IN A 128.8.10.90 ; BIND Create the /etc/namedb/named.local file.
The /etc/namedb/named.local file must contain the following information and be formatted as shown in the following example. Replace host1.cities.dec.com with your host and domain name. ; ; BIND data file for local loopback interface. ; @ IN SOA host1.cities.dec.com. postmaster.host1.cities.dec.com. (
                        1       ; Serial
                        3600    ; Refresh
                        300     ; Retry
                        3600000 ; Expire
                        3600 )  ; Minimum
    IN      NS      host1.cities.dec.com. 1 IN PTR localhost. localhost. IN A 127.0.0.1 Create the boot file.
The following is a sample named.boot file for a primary server. Replace cities.dec.com with your domain name and 120.105 with your network number: # @(#)named.boot # # Description: The named.boot file is required to boot a BIND # name server. # # Syntax: directory <directory_name> # ;[comment] # type domain source host/file # # <directory_name> Location where domain data files are stored. # ;[comment] Text following the ';' character is ignored. # type Specifies primary, secondary, or forwarder # server. # domain Name of the BIND domain. # source host IP address of the server distributing the # database listed under 'file'; not applicable # for primary servers. # file Name of database being distributed by # 'source host'. # directory /etc/namedb ; ; type domain source host/file primary cities.dec.com hosts.db primary 120.105.in-addr.arpa hosts.rev ; ; primary 0.0.127.in-addr.arpa named.local ; ; load the cache data last cache . named.ca
The database files are stored in the /etc/namedb directory by default. You can store database files in any directory; however, if you place them in a directory other than the default directory, you should change the /etc/namedb in the boot file to the name of the directory you have chosen. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following commands to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set BIND_CONF YES # /usr/sbin/rcmgr set BIND_SERVERTYPE PRIMARY # /usr/sbin/rcmgr set BIND_SERVERARGS "-b /etc/namedb/named.boot" Edit the /etc/hosts file with the fully qualified BIND name of the host.
To run BIND, your system's host name must include the BIND domain name. The fully qualified BIND host name consists of the local host name plus the BIND domain name, separated by dots. For example, the fully qualified BIND host name for a system whose local host name is host1 and whose BIND domain name is cities.dec.com is host1.cities.dec.com.
See the hosts(4) reference page for more information. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following command to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set HOSTNAME host1.cities.dec.com Replace host1.cities.dec.com with your system's fully qualified BIND name. Set the new host name with the /sbin/hostname command.
For example, to set the host name to host1.cities.dec.com for a system that was previously known locally as host1, enter the following command: # /sbin/hostname host1.cities.dec.com Start the named daemon by issuing the following command: # /sbin/init.d/named start
 

Setting Up a Secondary Server

Use the following procedure to set up a BIND secondary server: Create the /etc/resolv.conf file. See step 1 in the Setting Up the Primary Server section. Create the /etc/namedb/named.ca file. See step 3 in the Setting Up the Primary Server section. Create the /etc/namedb/named.local file. See step 4 in the Setting Up the Primary Server section. Create the boot file.

A boot file for a secondary server should have the format shown in the following example. Replace cities.dec.com with your domain name, 120.105 with your network number, and 120.105.4.5 with the IP address of your domain's BIND primary server: # @(#)named.boot # # Description: The named.boot file is required to boot a BIND # name server. # # Syntax: directory <directory_name> # ;[comment] # type domain source host/file # # <directory_name> Location where domain data files are stored. # ;[comment] text following the ';' character is ignored. # type Specifies primary, secondary, or forwarder # server. # domain Name of the BIND domain. # source host IP address of the server distributing the # database listed under 'file'; not applicable # for primary servers. # file Name of database being distributed by # 'source host'. # directory /etc/namedb ; ; type domain source host/file secondary cities.dec.com 120.105.4.5 hosts.db secondary 120.105.in-addr.arpa 120.105.4.5 hosts.rev ; ; primary 0.0.127.in-addr.arpa named.local ; ; load the cache data last cache . named.ca The following entry indicates that this host serves itself its own local host information: primary 0.0.127.in-addr.arpa named.local The default directory in which the database files are stored is /etc/namedb. You can store them in any directory; however, if you place them in a directory other than the default directory you should change the /etc/namedb at the top of the boot file to the name of the directory you have chosen. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following commands to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set BIND_CONF YES # /usr/sbin/rcmgr set BIND_SERVERTYPE SECONDARY # /usr/sbin/rcmgr set BIND_SERVERARGS "-b /etc/namedb/named.boot" Edit the /etc/hosts file to add the fully qualified BIND name of the host.

In order to run BIND, your system's host name must include the BIND domain name. The fully qualified BIND host name consists of the local host name plus the BIND domain name, separated by dots. For example, the fully qualified BIND host name for a system whose local host name is host2 and whose BIND domain name is cities.dec.com is host2.cities.dec.com.
See the hosts(4) reference page for more information. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following command to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set HOSTNAME host2.cities.dec.com Replace host2.cities.dec.com with your system's fully qualified BIND name. Set the new host name with the /sbin/hostname command.

For example, to set the host name to host2.cities.dec.com for a system that was previously known locally as host2, enter the following command: # /sbin/hostname host2.cities.dec.com Start the named daemon by issuing the following command: # /sbin/init.d/named start
 

Setting Up a Caching Server

Use the following procedure to set up a BIND caching server: Create the /etc/resolv.conf file. See step 1 in the Setting Up the Primary Server section. Create the /etc/namedb/named.ca file. See step 3 in the Setting Up the Primary Server section. Create the /etc/namedb/named.local file. See step 4 in the Setting Up the Primary Server section. Create the boot file.

The following is a sample named.boot file for a caching server. Replace information that is appropriate for a caching server in your domain: # @(#)named.boot # # Description: The named.boot file is required to boot a BIND # name server. # # Syntax: directory <directory_name> # ;[comment] # type domain source host/file # # <directory_name> Location where domain data files are stored. # ;[comment] Text following the ';' character is ignored. # type Specifies primary, secondary, or forwarder # server. # domain Name of the BIND domain. # source host IP address of the server distributing the # database listed under 'file'; not applicable # for primary servers. # file Name of database being distributed by # 'source host'. # directory /etc/namedb ; ; type domain source host/file primary 0.0.127.in-addr.arpa named.local ; ; load the cache data last cache . named.ca
The default directory in which the database files are stored is /etc/namedb. You can store them in any directory; however, if you place them in a directory other than the default directory you should change the /etc/namedb entry at the top of the boot file to the name of the directory you have chosen. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following commands to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set BIND_CONF YES # /usr/sbin/rcmgr set BIND_SERVERTYPE CACHING # /usr/sbin/rcmgr set BIND_SERVERARGS "-b /etc/namedb/named.boot" Edit the /etc/hosts file with the fully qualified BIND name of the host.

In order to run BIND, your system's host name must include the BIND domain name. The fully qualified BIND host name consists of the local host name plus the BIND domain name, separated by dots. For example, the fully qualified BIND host name for a system whose local host name is host3 and whose BIND domain name is cities.dec.com is host3.cities.dec.com.
See the hosts(4) reference page for more information. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following command to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set HOSTNAME host3.cities.dec.com Replace host3.cities.dec.com with your system's fully qualified BIND name. Set the new host name with the /sbin/hostname command.

For example, to set the host name to host3.cities.dec.com for a system that was previously known locally as host3, enter the following command: # /sbin/hostname host3.cities.dec.com Start the named daemon by issuing the following command: # /sbin/init.d/named start
 

Setting Up a Slave Server

Use the following procedure to set up a BIND slave server: Create the /etc/resolv.conf file. See step 1 in the Setting Up the Primary Server section. Create the /etc/namedb/named.local file. See step 4 in the Setting Up the Primary Server section. Create the boot file. The following is a sample named.boot file for a slave server. Replace 120.105.4.5 with the IP address of the BIND primary server in your domain: ; ; BIND data file to boot a slave name server. ; ; directory where all the data files are stored directory /etc/namedb ; ; type domain source host/file primary 0.0.127.in-addr.arpa named.local ; slave forwarders 120.105.4.5 The default directory in which the database files are stored is /etc/namedb. You can store them in any directory; however, if you place them in a directory other than the default directory you should change the /etc/namedb entry at the top of the boot file to the name of the directory you have chosen. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following commands to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set BIND_CONF YES # /usr/sbin/rcmgr set BIND_SERVERTYPE SLAVE # /usr/sbin/rcmgr set BIND_SERVERARGS "-b /etc/namedb/named.boot" Edit the /etc/hosts file and add the fully qualified BIND name of the host.

To run BIND, your system's host name must include the BIND domain name. The fully qualified BIND host name consists of the local host name plus the BIND domain name, separated by dots. For example, the fully qualified BIND host name for a system whose local host name is host4 and whose BIND domain name is cities.dec.com is host4.cities.dec.com.
See the hosts(4) reference page for more information. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following command to edit the /etc/rc.config file and add the required information: # /usr/sbin/rcmgr set HOSTNAME host4.cities.dec.com Replace host4.cities.dec.com with your system's fully qualified BIND name. Set the new host name with the /sbin/hostname command.

For example, to set the host name to host4.cities.dec.com for a system that was previously known locally as host4, enter the following command: # /sbin/hostname host4.cities.dec.com Start the named daemon by issuing the following command: # /sbin/init.d/named start
 

Setting Up a Client

Use the following procedure to set up a BIND client: Create the /etc/resolv.conf file.

The /etc/resolv.conf file for a client contains the domain name and IP addresses of up to three servers for the domain. These name servers are the systems that the local host can query to resolve host information. Format the /etc/resolv.conf file as follows, replacing your domain name for cities.dec.com and the IP addresses of your name servers for 120.105.4.5, 120.105.4.13, and 120.105.5.160: ; ; BIND data file ; domain cities.dec.com nameserver 120.105.4.5 nameserver 120.105.4.13 nameserver 120.105.5.160 See step 1 in the Setting up a Slave Server. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr utility. The syntax for the /usr/sbin/rcmgr command is as follows:

/usr/sbin/rcmgr set variable value

Enter the following commands to edit the /etc/rc.config file and add the required information:

# /usr/sbin/rcmgr set BIND_CONF YES # /usr/sbin/rcmgr set BIND_SERVERTYPE CLIENT

 

Post-Setup Procedures

After you configure BIND on your system, you must restart the sendmail process and edit the /etc/svc.conf file.  

Restarting the sendmail Process

To kill and restart the sendmail process, enter the following command: # /sbin/init.d/sendmail restart  

Editing the svc.conf File

The /etc/svc.conf file is the database service selection configuration file that your system references to determine what distributed database lookup services are running on your system, which databases are being served by them, and in what order to query them. After configuring BIND, you must edit the /etc/svc.conf file to tell your system that you want BIND servers queried for host name and address information. For information on editing the /etc/svc.conf file, see the svc.conf(4) and svcsetup(8) reference pages and the Network Administration manual.  

RELATED INFORMATION

bind_intro(7), bindconfig(8X), bindsetup(8), named(8), nslookup(8), resolv.conf(4), svc.conf(4) svcsetup(8)

Network Administration delim off


 

Index

NAME
DESCRIPTION
Setting Up the Primary Server
Setting Up a Secondary Server
Setting Up a Caching Server
Setting Up a Slave Server
Setting Up a Client
Post-Setup Procedures
Restarting the sendmail Process
Editing the svc.conf File
RELATED INFORMATION

This document was created by man2html, using the manual pages.
Time: 02:40:18 GMT, October 02, 2010