Installing and Administering Internet Services

Chapter 3 107
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
Following is an example boot file for a primary server authoritative for
the div.inc.com domain and for networks 15.19.8 and 15.19.13:
; domain source file
; type
;
directory /etc/named.data ;running directory for named
primary div.inc.com db.div
primary 0.0.127.IN-ADDR.ARPA db.127.0.0
primary 8.19.15.IN-ADDR.ARPA db.15.19.8
primary 13.19.15.IN-ADDR.ARPA
db.15.19.13
cache db.cache
Every name server must have data for the 0.0.127.IN-ADDR.ARPA
domain. Hosts running Berkeley networking use 127.0.0.1 as the address
of the loopback interface. Since the network number 127.0.0 is not
assigned to any one site but is used by all hosts running Berkeley
networking, each name server must be authoritative for network 127.0.0.
; Lines beginning with a semicolon (;) are comments.
directory Indicates the directory where data files are located.
primary Designates a primary server for the domain in the
second field. The third field is the name of the file
containing the data for that domain.
cache Indicates the location of the cache file, which contains
the addresses of network root name servers.
The Primary Master Server’s Cache File
The cache file, /etc/named.data/db.cache, lists the servers for the root
domain. Every name server must have a cache file. When a name server
cannot resolve a host name query from its local database or its local
cache, it queries a root server.
The hosts_to_named program creates the db.cache file, but it leaves it
empty. To add data to this file, copy it from the file
/usr/examples/bind/db.cache.arpa. You can also use anonymous ftp
to get the list of root name servers from nic.ddn.mil. Instructions are