Technical data

_________________________ Note _________________________
You should not manually edit the zone database file of a zone that is
being dynamically updated.
8.8 BIND Server Configuration Files
BIND reads information from an ASCII file called TCPIP$BIND.CONF. On
UNIX systems, the file name is
named.conf
. This configuration file consists of
statements that specify:
• The location of each BIND database file
• Global configuration options
• Logging options
• Zone definitions
• Information used for authentication
8.9 BIND Server Database Files
Files residing on BIND server systems contain the database of information needed
to resolve BIND queries. The following sections describe the four database files
used by the server:
• Master zone file
•Reversezonefile
• Loopback interface files
• Hints file
For detailed information about how to create and name these files, refer to the
Compaq TCP/IP Services for OpenVMS Management manual.
8.9.1 Master Zone File
A master server maintains the master zone file. This file contains:
• Start-of-authority (SOA) records, which specify the domain name for the zone,
a serial number, refresh time, retry and other administrative information
• NS records, which specify all the servers for the zone
• Address resource (A) records for each host in the zone
• MX records for mail servers
• CNAME records for specifying alias names for hosts
• Other various resource records
There is one master zone file for each zone for which the server has authority.
8.9.2 Reverse Zone File
For every host with an A record in the master zone file, an IP address must be
mapped back to a host name. This is accomplished by using a zone file for a special
domain called the IN-ADDR.ARPA domain.
The zone file for this domain contains PTR records that specify the reverse
translations (address-to-host name) required for the zone. There is an
8–8 Domain Name System/BIND (DNS/BIND)