named.conf.4 (2010 09)

n
named.conf(4) named.conf(4)
(BIND 9.3)
optionally a zone name, and optionally a view name. The lines without view and zone listed are global
statistics for the entire server. Lines with a zone and view name are for the given view and zone (the
view name is omitted for the default view). The statistics dump ends with the line
--- Statistics Dump --- (973798949)
where the number is identical to the number in the beginning line.
The following statistics counters are maintained:
success The number of successful queries made to the server or zone. A successful query is
defined as query which returns a NOERROR response other than a referral response.
referral The number of queries which resulted in referral responses.
nxrrset The number of queries which resulted in NOERROR responses with no data.
nxdomain The number of queries which resulted in NXDOMAIN responses.
recursion The number of queries which caused the server to perform recursion in order to find the
final answer.
failure The number of queries which resulted in a failure response other than those above.
ZONE FILES
A zone file is a text file that defines a zone, designating a domain name, with all of its associated sub-
domains, IP addresses, and mail servers. It may contain directives, resource records, and comments.
Blank lines may be included for readability. A zone definition starts with an
SOA
resource record. The
zone file name is used in the
file substatement of a zone statement in the named
configuration file,
/etc/named.conf.
A zone consists of those contiguous parts of the domain tree for which a domain server has complete
information and over which it has authority. A domain server may be authoritative for more than one
zone.
An absolute domain name or fully qualified domain name (FQDN) in a zone file is one that ends in a
period (
.). For example, example.com. is an absolute domain name.
A relative domain name in a zone file does not end in a period. For example,
myhost.example is a
relative domain name.
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.
30 Hewlett-Packard Company − 30 − HP-UX 11i Version 3: September 2010