19.3. Zone Files
namedworking directory (
/var/named/) by default. Each zone file is named according to the
fileoption data in the
zonestatement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as
bind-chrootpackage, the BIND service will run in the
/var/named/chrootenvironment. All configuration files will be moved there. As such, you can find the zone files in
;) in zone files.
19.3.1. Zone File Directives
$) followed by the name of the directive. They usually appear at the top of the zone file.
namedto include another zone file in this zone file at the place where the directive appears. This allows additional zone settings to be stored apart from the main zone file.
- Appends the domain name to unqualified records, such as those with the hostname and nothing more.For example, a zone file may contain the following line:
$ORIGIN example.com.Any names used in resource records that do not end in a trailing period (
.) are appended with
NoteThe use of the
$ORIGINdirective is unnecessary if the zone is specified in
/etc/named.confbecause the zone name is used as the value for the
$ORIGINdirective by default.
- Sets the default Time to Live (TTL) value for the zone. This is the length of time, in seconds, that a zone resource record is valid. Each resource record can contain its own TTL value, which overrides this directive.Increasing this value allows remote nameservers to cache the zone information for a longer period of time, reducing the number of queries for the zone and lengthening the amount of time required to proliferate resource record changes.