Table of Contents
Advertisement
Chapter 12. Berkeley Internet...
2.3. Comment Tags
The following is a list of valid comment tags used within
•
— When placed at the beginning of a line, that line is ignored by
//
•
— When placed at the beginning of a line, that line is ignored by
#
•
and
— When text is enclose in these tags, the block of text is ignored by
/*
*/
3. Zone Files
Zone files contain information about a namespace and are stored in the
directory,
/var/named/
the
statement, usually in a way that relates to the domain in question and identifies the file
zone
as containing zone data, such as
Each zone file may contain 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. Directives are optional, but resource records
are required to provide name service to a zone.
All directives and resource records should be entered on individual lines.
Comments can be placed after semicolon characters (
3.1. Zone File Directives
Directives begin with the dollar sign character (
usually appear at the top of the zone file.
The following are commonly used directives:
•
— Configures
$INCLUDE
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
$ORIGIN
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 (
.
example.com
222
, by default. Each zone file is named according to the
example.com.zone
to include another zone file in this zone file at the place where
named
:
named.conf
.
) in zone files.
;
) followed by the name of the directive. They
$
.
named
.
named
.
named
working
named
option data in
file
) are appended with
.
Advertisement
Table of Contents
