HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

n
named.conf(4) named.conf(4)
(BIND 9.3)
the rule will apply to multiple identities. The identity field must contain a fully qualified domain name.
The nametype field has four possible values:
name Exact-match semantics. This rule matches when the name being updated is identical to the
contents of the name field.
subdomain This rule matches when the name being updated is a subdomain of, or identical to, the con-
tents of the name field.
wildcard The name field is subject to DNS wildcard expansion, and this rule matches when the name
being updated is a valid expansion of the wildcard.
self This rule matches when the name being updated matches the contents of the identity field.
The name field is ignored, but should be the same as the identity field. The
self name-
type is most useful when allowing the use of one key per name to update, where the key
has the same name as the name to be updated. The identity would be specified as
* in this
case.
In all cases, the name field must specify a fully qualified domain name.
If no types are explicitly specified, this rule matches all types except
SIG, NS
, SOA, and XT.Atype may
be specified by name, including
ANY (which matches all types except NXT, which can never be updated).
Note that when an attempt is made to delete all records associated with a name, the rules are checked for
each existing record type.
The Statistics File
The statistics file generated by BIND 9.3 is similar, but not identical, to that generated by BIND 8. The
statistics dump begins with the line
+++ Statistics Dump +++ (973798949)
where the number in parentheses is a standard UNIX-style time stamp, measured as seconds since January
1, 1970. Following that line are a series of lines containing a counter type, the value of the counter, option-
ally 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 infor-
mation 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.
HP-UX 11i Version 3: February 2007 − 29 − Hewlett-Packard Company 261