HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)
n
named.conf(4) named.conf(4)
(BIND 9.3)
An origin in a zone file is an absolute domain name that is appended to a relative domain name to com-
plete it. For example, if example.com.
is the origin and myhost is a relative domain name, they
would combine to form the absolute domain name,
myhost.example.com.
.
A comment starts with a semicolon (
;
) and continues to the end of the line. A comment can appear on a
line by itself or at the end of any directive or resource record line, including lines that are continued. For
example, in the following record,
; Mail exchange
is a comment.
hostname IN MX 10 mailhost.example.com. ; Mail exchange
Records normally end at the end of a line. However, they may be continued across lines if the text is
enclosed in parentheses, (...). See the example in the SOA Resource Records section.
Zone File Directives
Zone file directives help to simplify resource records. The directives include
$ORIGIN, $INCLUDE,
$TTL, and $GENERATE.
The $ORIGIN Directive
The $ORIGIN directive sets the origin that will be appended to any subsequent relative domain names.
This provides a convenient shorthand for writing resource records.
Syntax
$ORIGIN origin
origin A domain name that serves as the suffix for subsequent relative domain names.
When named starts, the default origin is the zone_name in the zone statement of the configuration file,
/etc/named/conf.
If the new origin is not absolute (does not have a terminating period), the old origin is appended to it.
For example,
$ORIGIN com.
$ORIGIN example
WWW CNAME MAIN-SERVER
is equivalent to:
$ORIGIN example.com.
WWW CNAME MAIN-SERVER
is equivalent to:
WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
The $INCLUDE Directive
The
$INCLUDE directive reads and processes a file as if it were included into the file at this point.
Syntax
$INCLUDE filename [ origin ]
filename The name of the file to be included.
origin The origin for the data in the included file. The default is the current origin of the includ-
ing (parent) file.
Neither the origin field nor $ORIGIN statements in the included file affect the origin of the parent file.
Once the included file has been processed, the origin and the current record owner name revert to the
values they had prior to the $INCLUDE directive.
Note: RFC 1035 specifies that the current origin should be restored after an $INCLUDE, but it is silent on
whether the current record owner name should also be restored. BIND 9 restores both of them. This could
be construed as a deviation from RFC 1035, a feature, or both.
The $TTL Directive
The $TTL directive sets the default Time to Live (TTL) value for subsequent RRs that have undefined
TTLs.
262 Hewlett-Packard Company − 30 − HP-UX 11i Version 3: February 2007