Installing and Administering Internet Services

114 Chapter3
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
IN HINFO HP9000/850 HPUX
IN WKS 15.19.8.64 UDP syslog domain
route
IN WKS 15.19.8.64 TCP (telnet smtp
ftp
shell domain)
rabbit IN MX 5 rabbit.div.inc.com.
IN MX 10 indigo.div.inc.com.
rabbit IN A 15.19.8.119
The Primary Master Server’s db.net Files
A primary server has one db. net file for each network it serves. net is
the network number specified with the -n option in the hosts_to_named
command. This file should contain a PTR (pointer) record for every host in
the zone. A PTR record allows BIND to translate an IP address back into
its host name. BIND resolves the address of a name by tracing down the
domain tree and contacting a server for each label of the name.
The in-addr.arpa domain was created to allow this inverse mapping.
The in-addr.arpa domain is preceded by four labels corresponding to
the four bytes (octets) of an internet address. Each byte must be specified
even if it is zero. For example, the address 143.22.0.3 has the domain
name 3.0.22.143.in-addr.arpa. Note that the four octets of the
address are reversed.
;
; db.15.19.8
;
@ 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