Sample /etc/named.boot file
The file /etc/named.boot contains information about
the location of cache, database, and other
name server files, and other information that is read each time
the DNS daemon, named, starts.
Here is a sample named.boot file:
; ; Name Server boot file for primary name server volga for domain mynet.COM ; ; Type Domain Source file or Host ; directory /etc/named.d primary mynet.COM mynet.hosts primary 147.132.in-addr.arpa mynet.rev primary 0.0.127.in-addr.arpa named.local secondary ucsc.edu 128.114.129.22 ucsc.bak stub sub.mynet.COM 132.147.24.1 sub.mynet.com.stub bogusns 132.147.118.3 xfernets 132.147.246.8 cache . root.cache
If multiple servers appear on a secondary line, each server is tried in the order listed until a successful zone transfer occurs. When the server starts, the backup file is loaded and a primary server is then consulted to check that the zone is still up-to-date.
You do not need a special line to designate that a server is a caching server. A caching-only server is indicated by the absence of authority lines, such as secondary or primary in the boot file.
Two additional entries cover the use of forwarders:
forwarders 132.147.246.5 132.147.246.8 slaveThe first entry causes the server to forward requests to the first IP address listed: a server elsewhere on the net. If no response is received, the second server is tried. If unsuccessful again, it follows its default resolution procedure, either examining its cache, contacting other servers, or both.
The second entry, slave
, restricts resolution further.
A server acting in
slave mode may only contact forwarders.
See also: