Installing and Administering Internet Services

Chapter 3 79
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
1.0.0.127.in-addr.arpa. (The current origin is
appended to the 1 in the name field, because it does not
end with a dot.)
data The SOA data includes the name of the host this data
file was created on, the mailing address of the person
responsible for the name server, and the following
values:
Serial The version number of this file,
incremented whenever the data is
changed.
Refresh Indicates (in seconds) how often a
secondary name server should try to
update its data from a master server.
Retry Indicates (in seconds) how often a
secondary server should retry after
an attempted refresh fails.
Expire Indicates (in seconds) how long the
secondary name server can use the
data before it expires for lack of a
refresh.
Minimum ttl The minimum number of seconds for
the time to live field on other resource
records for this domain.
The NS data is the fully qualified name of the name
server.
The PTR data is the loopback address of localhost, in
the in-addr.arpa domain.
The Primary Master Server’s db.domain Files
A primary 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 should contain an A (address) record for every host in the zone.
The example file shown below, db.div, contains the following types of
records: