Product SiteDocumentation Site

11.2.2. ゾーンファイルの編集

As outlined in 「ネームサーバーゾーン」, zone files contain information about a namespace. They are stored in the named working directory located in /var/named/ by default, and each zone file is named according to the file option in the zone statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as
表11.5 The named service zone files
パス 説明
/var/named/ named サービスの作業ディレクトリです。ネームサーバーはこのディレクトリに書き込みが許可されません
/var/named/slaves/ セカンダリ・ゾーン向けのディレクトリです。このディレクトリは named サービスにより書き込み可能です。
/var/named/dynamic/ The directory for other files, such as dynamic DNS (DDNS) zones or managed DNSSEC keys. This directory is writable by the named service.
/var/named/data/ The directory for various statistics and debugging files. This directory is writable by the named service.

A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
すべてのディレクティブとリソースレコードは、個々の行に記載する必要があります。 Common Directives

Directives begin with the dollar sign character (that is, $) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
The $INCLUDE directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
例11.6 Using the $INCLUDE directive
$INCLUDE /var/named/

The $ORIGIN directive allows you to append the domain name to unqualified records, such as those with the hostname only. Note that the use of this directive is not necessary if the zone is specified in /etc/named.conf, since the zone name is used by default.
In 例11.7「$ORIGIN ディレクティブの使用法」, any names used in resource records that do not end in a trailing period (that is, the . character) are appended with
例11.7 $ORIGIN ディレクティブの使用法

The $TTL directive allows you to set the default Time to Live (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
例11.8 $TTL ディレクティブの使用
$TTL 1D Common Resource Records

The following resource records are commonly used in zone files:
The Address record specifies an IP address to be assigned to a name. It takes the following form:
hostname IN A IP-address
If the hostname value is omitted, the record will point to the last specified hostname.
In 例11.9「A リソースレコードの使用法」, the requests for are pointed to or
例11.9 A リソースレコードの使用法
server1  IN  A
         IN  A

The Canonical Name record maps one name to another. Because of this, this type of record is sometimes referred to as an alias record. It takes the following form:
alias-name IN CNAME real-name
CNAME records are most commonly used to point to services that use a common naming scheme, such as www for Web servers. However, there are multiple restrictions for their usage:
  • CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
  • CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, NSEC, etc.) when the zone is signed.
  • Other resource record that point to the fully qualified domain name (FQDN) of a host (that is, NS, MX, PTR) should not point to a CNAME record.
In 例11.10「CNAME リソースレコードの使用法」, the A record binds a hostname to an IP address, while the CNAME record points the commonly used www hostname to it.
例11.10 CNAME リソースレコードの使用法
server1  IN  A
www      IN  CNAME  server1

The Mail Exchange record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
IN MX preference-value email-server-name
The email-server-name is a fully qualified domain name (FQDN). The preference-value allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The MX resource record with the lowest preference-value is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
In 例11.11「MX リソースレコードの使用法」, the first email server is preferred to the email server when receiving email destined for the domain.
例11.11 MX リソースレコードの使用法  IN  MX  10
              IN  MX  20

IN NS nameserver-name
The nameserver-name should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
例11.12 NS リソースレコードの使用法

ポインター レコードは、名前空間の他の場所を示します。以下の形式をとります:
last-IP-digit IN PTR FQDN-of-system
The last-IP-digit directive is the last number in an IP address, and the FQDN-of-system is a fully qualified domain name (FQDN).
PTR records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to 「逆引き名前解決ゾーンファイル」 for more examples of PTR records in use.
The Start of Authority record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
@  IN  SOA  primary-name-server hostmaster-email (
       minimum-TTL )
  • The @ symbol places the $ORIGIN directive (or the zone's name if the $ORIGIN directive is not set) as the namespace being defined by this SOA resource record.
  • The primary-name-server directive is the hostname of the primary nameserver that is authoritative for this domain.
  • The hostmaster-email directive is the email of the person to contact about the namespace.
  • The serial-number directive is a numerical value incremented every time the zone file is altered to indicate it is time for the named service to reload the zone.
  • The time-to-refresh directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
  • The time-to-retry directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the time-to-expire directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
  • In BIND 4 and 8, the minimum-TTL directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (that is, 3H).
When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (M), hours (H), days (D), and weeks (W). 表11.6「他の時間単位と比較した秒数」 shows an amount of time in seconds and the equivalent time in another format.
表11.6 他の時間単位と比較した秒数
60 1M
1800 30M
3600 1H
10800 3H
21600 6H
43200 12H
86400 1D
259200 3D
604800 1W
31536000 365D

例11.13 SOA リソースレコードの使用法
@  IN  SOA (
       2001062501  ; serial
       21600       ; refresh after 6 hours
       3600        ; retry after 1 hour
       604800      ; expire after 1 week
       86400 )     ; minimum TTL of 1 day コメントタグ

Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the named service, but can prove useful when providing additional information to the user. Any text after the semicolon character (that is, ;) to the end of the line is considered a comment. For example:
   604800  ; 1 週間後に期限切れ 使用例

以下の例はゾーンファイルの基本的な使用法を示しています。 簡単なゾーンファイル
例11.14「簡単なゾーンファイル」は標準的なディレクティブと SOA 値の使用法を説明します。
例11.14 簡単なゾーンファイル
$TTL 86400
@         IN  SOA (
              2001062501  ; serial
              21600       ; refresh after 6 hours
              3600        ; retry after 1 hour
              604800      ; expire after 1 week
              86400 )     ; minimum TTL of 1 day
          IN  NS
          IN  NS
dns1      IN  A
          IN  AAAA   aaaa:bbbb::1
dns2      IN  A
          IN  AAAA   aaaa:bbbb::2
@         IN  MX     10
          IN  MX     20
mail      IN  A
          IN  AAAA   aaaa:bbbb::5
mail2     IN  A
          IN  AAAA   aaaa:bbbb::6
; This sample zone file illustrates sharing the same IP addresses
; for multiple services:
services  IN  A
          IN  AAAA   aaaa:bbbb::10
          IN  A
          IN  AAAA   aaaa:bbbb::11

ftp       IN  CNAME
www       IN  CNAME

In this example, the authoritative nameservers are set as and, and are tied to the and IP addresses respectively using the A record.
The email servers configured with the MX records point to mail and mail2 via A records. Since these names do not end in a trailing period (that is, the . character), the $ORIGIN domain is placed after them, expanding them to and
Services available at the standard names, such as (WWW), are pointed at the appropriate servers using the CNAME record.
このゾーンファイルは、/etc/named.conf ファイルにおいて、以下のような zone ステートメントを用いたサービスの中に呼び出されます:
zone "" IN {
  type master;
  file "";
  allow-update { none; };
}; 逆引き名前解決ゾーンファイル
逆引き名前解決ゾーンファイルは、特定の名前空間にある IP アドレスを完全修飾ドメイン名(FQDN)に変換するために使用されます。これは、例11.15「逆引き名前解決ゾーンファイル」にあるよように、PTR リソースレコードが IP アドレスを完全修飾ドメイン名にリンクするために使用されることを除いて、標準的なゾーンファイルによく似ています。
例11.15 逆引き名前解決ゾーンファイル
$TTL 86400
@  IN  SOA (
       2001062501  ; serial
       21600       ; refresh after 6 hours
       3600        ; retry after 1 hour
       604800      ; expire after 1 week
       86400 )     ; minimum TTL of 1 day
@  IN  NS
1  IN  PTR
2  IN  PTR
5  IN  PTR
6  IN  PTR
3  IN  PTR
4  IN  PTR

この例において、IP アドレス から は対応する完全修飾ドメイン名に対応づけられます。
このゾーンファイルは、/etc/named.conf ファイルにおいて、以下のような zone ステートメントを用いたサービスの中に呼び出されます:
zone "" IN {
  type master;
  file "";
  allow-update { none; };
There is very little difference between this example and a standard zone statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the IP address reversed followed by This allows the single block of IP numbers used in the reverse name resolution zone file to be associated with the zone.