Configuring and Managing MPE/iX Internet Services (August 2002)

Chapter 8
DNS BIND/iX
Data Files
124
1 IN PTR m1.india.hp.com.
2 IN PTR m2.india.hp.com.
3 IN PTR m3.india.hp.com.
4 IN PTR m4.india.hp.com.
5 IN PTR m5.india.hp.com.
Configuring Slave Zones
A sample configuration unit for a slave zone is shown here:
zone “41.10.15.IN-ADDR.ARPA” {
type slave;
file “zone.15.10.41”;
masters {
15.70.188.45;
};
};
The IP address of the server that is primary for that domain is specified in the masters { } section of the
configuration. There could be more than one master for a given zone.
When the nameserver comes up, looking at this configuration, it makes a connection with the nameserver
running on 15.70.188.45 and does zone transfer, if required. It also makes a local copy of this file.
Data Files
The files that the primary nameservers load their zone data from are called data files or zone files. They are
also referred to as db files, short for database files.
The data files contain resource records that describe the zone. The resource records describe all the hosts in
the zone.
Root Cache Data (Hint File)
Besides your local information, the nameserver also needs to know where the nameservers for the root
domain are. This information must be retrieved from the Internet host ftp.rs.internic.net.
Explaining DNS Database Files
This is a typical DNS zone.domain file for the domain maxx.net. (Its name would be zone.maxx.net. It will
translate from a host name to its IP address.)
;
; Addresses for the local domain
maxx.net. IN SOA nova.maxx.net. tyager.nova.maxx.net. (
9602171 ; Serial
36000 ; Refresh every 10 hours
3600 ; Retry after 1 hour
360000 ; Expire after 100 hours
36000 ; Minimum TTL is 10 hours )
; Define name servers
;
maxx.net. IN NS nova.maxx.net.
maxx.net. IN A 204.251.17.241