NAMED zone data files

Apart from general configuration settings, the file /etc/named.conf also contains information on the zones to be set up. The actual zone data is stored in local system files as Resource Records and read from these system files on starting the server daemon.

The syntax of the local zone data files is described in the “BIND9 Administrator Reference Manual” of the Internet Software Consortium.

All zone data files must be created in the SRR (Standard Resource Record) format, where each line of the file contains one Resource Record (RR).

Example

Structure of the masterzone file

test1.mch.fj.example.  IN  SOA  host1.test1.mch.fj.example.  postmaster (
                       1 ; serial
                       10800 ;    Refresh after 3 hours
                       3600 ;     Retry after 1 hour
                       604800 ;   Expire after 1 week
                       86400) ;   Minimum TTL of 1 day
;
;  Name servers
;
test1.mch.fj.example.  IN    NS     host1.test1.mch.fj.example.
                         IN    NS     host2.test1.mch.fj.example.
;
;  Addresses
;
host1             IN     A        155.60.70.1
host2             IN     A        155.60.70.2
host3             IN     A        155.60.70.3
loopback          IN     A        127.0.0.1
;  Aliases
;
alias1            IN    CNAME        host1.test1.mch.fj.example.
;
;   Mail Exchanger
;
test1.mch.fj.example.    IN    MX    0      host1.test1.mch.fj.example.
test1.mch.fj.example.    IN    MX    10     host3.test1.mch.fj.example.

Example

Structure of the arpafile file

60.155.in_addr.arpa.    IN   SOA   host1.test1.mch.fj.example.postmaster (
                                  postmaster (
                        1       ; serial
                        10800   ; Refresh after 3 hours
                        3600    ; Retry after 1 hour
                        604800  ;  Expire after 1 week
                        86400)  ;  Minimum TTL of 1 day
;
;  Name servers
;
60.155.in_addr.arpa.     IN  NS     host1.test1.mch.fj.example.
                         IN  NS     host2.test1.mch.fj.example.
;
;  Addresses
;
1.70            IN         PTR     host1.test1.mch.fj.example.
2.70            IN         PTR     host2.test1.mch.fj.example.
3.70            IN         PTR     host3.test1.mch.fj.example.

Example

Structure of the loopback file

0.0.127.in_addr.arpa.  IN  SOA  host1.test1.mch.fj.example.
                                 postmaster (
                       10800   ; Refresh after 3 hours
                       3600    ; Retry after 1 hour
                       604800  ; Expire after 1 week
                       86400)  ; Minimum TTL of 1 day
;
;  Name servers
;
0.0.127.in_addr.arpa.  IN  NS     host1.test1.mch.fj.example.
;
;  Addresses
;
1.0.0.127.in_addr.arpa.  IN  PTR    localhost.