Installing and Administering Internet Services

Chapter 3 83
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
@ IN SOA rabbit.div.inc.com. root.moon.div.inc.com.(
1 ; Serial
10800 ; Refresh every 3 hours
3600 ; Retry every hour
604800 ; Expire after a week
86400 ) ; Minimum ttl of 1 day
IN NS rabbit.div.inc.com.
IN NS indigo.div.inc.com.
119 IN PTR rabbit.div.inc.com.
64 IN PTR cheetah.div.inc.com.
197 IN PTR indigo.div.inc.com.
This example file, db.15.19.8, contains the following records:
SOA Start of Address record. The SOA record designates the
start of a domain, and indicates that this server is
authoritative for the data in the domain.
In data files, @ represents the current origin. The
current origin is the domain configured in this file,
according to the boot file. The boot file says that the
8.19.15.in-addr.arpa domain is configured in the
db.15.19.8 file. Therefore, every instance of @ in the
db.15.19.8 file represents 8.19.15.in-addr.arpa.
The SOA record indicates 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.