Technical data

Configuring and Managing BIND
5.4 Populating the BIND Server Databases
IN Identifies the record as an Internet DNS resource record.
type Identifies what kind of resource record this is. (See Table 5–11 for the
record types you can specify.)
data Information specific to this type of resource record. For example, in an
A record, this is the field that contains the actual IP address.
5.4.3 Saving Backup Copies of Zone Data
The name server saves backup copies of the zone data in
SYS$SPECIFIC:[TCPIP$BIND]. Do not delete these backup copies. When
the master server is down and the secondary server is started, the secondary
server cannot perform a zone transfer until the master server is up. However,
with backup copies, the secondary server has some data (though possibly out of
date) to perform its basic tasks.
5.4.4 Sample Database Files
The following sections provide sample BIND database files.
5.4.4.1 Local Loopback: Forward and Reverse Translation Files
In the LOCALHOST.DB file, the local host address is usually 127.0.0.1. The
following sample LOCALHOST.DB file shows the forward translation for the local
loopback interface.
;
; BIND data file for local loopback interface (forward
translation).
;
; Provided for Compaq TCP/IP Services for OpenVMS.
;
$ORIGIN localhost.
@ 1D IN SOA @ root (
42 ;Serial
3H ;Refresh
15M ;Retry
1W ;Expiry
1D ) ;Minimum
;
1D IN NS @
1D IN A 127.0.0.1
The following sample 127_0_0.DB file shows the reverse translation for the local
loopback interface.
;
; BIND data file for local loopback interface (reverse
translation).
;
; Provided for Compaq TCP/IP Services for OpenVMS.
;
$ORIGIN 0.0.127.in-addr.arpa.
@ 1D IN SOA localhost.
root.localhost. (
42 ;Serial
3H ;Refresh
15M ;Retry
1W ;Expiry
1D ) ;Minimum
;
1D IN NS localhost.
1 1D IN PTR localhost.
Configuring and Managing BIND 5–27