Master Server db.domain Files
The Berkeley Internet Name Domain (BIND) is a distributed network information lookup service. It allows you to retrieve host names and Internet addresses for any node on the network. It also provides mail routing capability by supplying a list of hosts that accept mail for other hosts
You can configure your host as any of the following types of BIND name servers:
>
- >
A master server is the authority for its domain and contains data corresponding to its domain. The master server obtains its information from a master file on the disk. On previous versions of BIND, the master server was referred to as a primary server.
- >
Slave Server
A slave server is also the authority for its domain and contains the domain’s data, but it receives data over a network fromanother master server. On previous versions of BIND, the slave server was referred to as a secondary server.
- >
A caching-only server is not authoritative for any domain. The only function that a caching-only server performs is to look up data from an authoritative server and store the data in its cache.
- >
A forwarding server always forwards queries that it cannot satisfy from its authoritative data or cache to a fixed list of other servers. A forwarding server is typically used when you do not want all the servers at a given site to interact with the rest of the Internet servers. An added benefit of using the forwarding feature is that the forwarding server develops a complete cache of information that all the workstations can use.
If you do not want to run a name server on your host, you can configure the resolver to query a name server on another host. By default, the resolver is configured to query the name server on the local host.
 |
|
|
|
|
|
 |
NOTE: Throughout this document, the terms zone and domain are used interchangeably, though they describe different concepts. A zone describes the domain name spacethat a name server has authority over. As such, a zone does not contain any delegated subdomains, whereas a domain can contain data delegated to other name servers. Therefore, as long as subdomains are not delegated, a zone and a domain contain the same data. |
|
|
|
|
|
|
>>>>
Choosing the Type of Name Server |
|
>
You can use any server configuration on a host. Following are some suggestions for the configuration:
>
- >
You must configure timeshare machines or cluster servers as master or slave servers.
- >
If you want the benefits of a name server but do not want to maintain authoritative data, you can set up a caching-only server. Running a caching-only server provides you better performance than querying a name server on a remote system, especially if the remote system is on the other side of a gateway or router.
- >
You must configure PCs, workstations that do not want to maintain a server, and other small networked systems to query a name server on another host. Cluster nodes must query the name server on the cluster server.
- >
If your network is isolated from the Internet, and your host is the only BIND name server in your organization, you must configure a root name server. See “Configuring a Root Name Server” for information.
The configuration file, /etc/named.conf, informs the master server of the location of all the required data files. The master name server loads its database from these data files. The hosts_to_named program creates the named.conf file.
Following is an example configuration file for a master server authoritative for the domain div.inc.com, and for the network 15.19.8.
|
|
|
Figure 2-1 “Structure of a Master Server and Slave Servers” shows the structure of a master server and a slave server. In the Figure 2-1 “Structure of a Master Server and Slave Servers”, the master server is rabbit.div.inc.com and the slave servers are cheetah.div.inc.com and indigo.div.inc.com.
Figure 2-1 Structure of a Master Server and Slave Servers
|
|
|
|
Master server data File
A master server has one /etc/named.data/db.domain file for each domain for which it is authoritative. domain is the first part of the domain specified with the -d option in the hosts_to_named command. This file must contain an A (address) record for every host in the zone.
The following is an example db.div file:
|
|
|
The example file db.div contains the following types of records:
>
The above resources is from www.hp.com.
Detailed information about BIND9, Please reffer to www.bind9.net
