HP-UX Reference (11i v2 04/09) - 1M System Administration Commands N-Z (vol 4)
n
named(1M) named(1M)
10.2.0.78;
};
};
key rndc_key {
algorithm "hmac-md5";
secret "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};
controls {
inet 127.0.0.1 allow { 127.0.0.1; } keys { rndc_key; };
};
zone "." {
type hint;
file "db.cache";
};
zone "berkeley.edu" {
type master;
file "db.berkeley";
};
zone "32.128.in-addr.arpa" {
type master;
file "db.128.32";
};
zone "cc.berkeley.edu" {
type slave;
file "db.cc";
masters {
128.32.137.8;
};
};
The
directory statement changes the working directory of the server to the directory specified. The
working directory specified is relative to the new root directory if set by the
-t option. This can be
important for the correct processing of
$INCLUDE files (described later) in primary server’s master files.
Files referenced in the configuration file contain data in the master file format described in RFC 1035.
The
key statement names a key with its string argument. The string has to be a valid domain name.
However, this need not be hierarchical; thus, a string "rndc_key" is a valid name.
The
key statement has two clauses: algorithm and secret. The configuration parser will accept any
string as the argument to algorithm. However, only the string "hmac-md5" is supported for accepting
control messages from the utility, rndc. See rndc(1) and rndc.conf (4). The secret is a base-64
encoded string, typically generated with dnssec-keygen.
The
controls statement is used to configure the name server to accept connections from the utility,
rndc which controls the name server. The key specified in this statement should match the one set in
the rndc configuration file, rndc.conf.
The
forwarders line specifies the addresses of sitewide servers that will accept recursive queries from
other servers. If the configuration file specifies one or more forwarders, then the server will send all
queries for data not in the cache or in its authoritative data to the forwarders first. Each forwarder will
be asked in turn until an answer is returned or the list is exhausted. If no answer is forthcoming from a
forwarder, the server will continue as it would have without the forwarders line unless it is in
forward-only mode. The forwarding facility is useful to cause a large sitewide cache to be generated
on a master, and to reduce traffic over links to outside servers.
The
noforward line specifies that the DNS server will not forward any request for something in or
below the listed domains, even if the forwarders directive exists.
A server can access information from servers in other domains given a list of root name servers and their
addresses. The
zone "." line specifies that data in db.cache is to be placed in the backup cache. Its
HP-UX 11i Version 2: September 2004 − 2 − Hewlett-Packard Company Section 1M−−497