TCP/IP Configuration and Management Manual

Configuration Reference
TCP/IP Configuration and Management Manual—427132-004
A-10
Domain Name Server Files
Example Boot Files
The following section contains sample boot files for the different types of servers. A
boot file is the startup file that specifies the mode of operation and specifies other
information to NAMED. The boot file is named $SYSTEM.ZTCPIP.DNSBOOT
Primary Master Server
In this example of a boot file, the domain name server is set to act as a primary master
server:
;
; Boot file for Primary Master Name Server
;
; type domain source file or host
;
domain kentcomm.com
primary kentcomm.com $SYSTEM.ZTCPIP.DNSHOSTS
primary 33.128.in-addr.arpa $SYSTEM.ZTCPIP.DNSREV
primary 0.0.127.in-addr.arpa $SYSTEM.ZTCPIP.DNSLOCAL
cache . $SYSTEM.ZTCPIP.DNSCACHE
The domain specified is kentcomm.com. The domain name server that uses this boot
file is a primary for this domain and a primary for reverse-address mapping in the
special domain IN-ADDR.ARPA. The domain name server is to load its cache from the
file $SYSTEM.ZTCPIP.DNSCACHE.
Secondary Master Server
In this example of a boot file, a domain name server is set to act as a secondary
master server:
;
; Boot file for Secondary Master Name Server
;
; type domain source file or host
domain kentcomm.com
secondary kentcomm.com 128.33.0.14 $SYSTEM.ZTCPIP.DNSBAK
secondary 33.128.in-addr.arpa 128.33.0.11
$SYSTEM.ZTCPIP.DNREVBAK
primary 0.0.127.in-addr.arpa $SYSTEM.ZTCPIP.DNSLOCAL
cache . $SYSTEM.ZTCPIP.DNSCACHE
In this example, you may specify more than one address on the secondary line. Use
spaces to separate the addresses. The domain name server that uses this example
boot-file is the secondary for the domain kentcomm.com. The server downloads its
database from the address 128.33.0.14 and writes this information to the file
$SYSTEM.ZTCPIP.DNSBAK.
If the secondary server cannot access the primary domain-name server’s database at
boot time, it loads its database from the file $SYSTEM.ZTCPIP.DNSBAK (if the file
exists). When the secondary server can contact the primary, it checks to see if the
primary has a different serial number (see the SOA—Start Of Authority
on page A-16).