HP-UX Reference (11i v2 04/09) - 4 File Formats (vol 8)

n
named.conf(4) named.conf(4)
statistics-file
The pathname of the file in which the server appends statistics using
rndc stats.
Default is
named.stats in the server’s current directory.
port The UDP/TCP port number the server uses for receiving and sending DNS protocol
traffic. Default is 53. This option is mainly intended for server testing; a server using a
port other than 53 will not be able to communicate with the global DNS.
random-device
The source of entropy to be used by the server. Entropy is primarily needed for DNSSEC
operations, such as TKEY transactions and dynamic update of signed zones. This option
specifies the device (or file) from which to read entropy. If this is a file, operations
requiring entropy will fail when the file has been exhausted. The default value is
/dev/random (or equivalent) when present, and none otherwise. The
random-
device option takes effect during the initial configuration load at server startup time
and is ignored on subsequent reloads.
Boolean Options
auth-nxdomain
If "yes", then the AA bit is always set on NXDOMAIN responses, even if the server is not
actually authoritative. The default is "no". If you are using an old version of BIND, you
might need to set this option to "yes".
dialup If "yes", then the server treats all zones as if they are doing zone transfers across a dial on
demand dialup link, which can be brought up by traffic originating from this server. This
has different effects according to zone type and concentrates the zone maintenance so that it
all happens in a short interval, once every heartbeat-interval and hopefully during the one
call. It also suppresses some of the normal zone maintenance traffic. The default is "no".
The dialup option may also be specified in the view and zone statements, in which case, it
overrides the global dialup option.
If the zone is a master zone then the server will send out a NOTIFY request to all the slaves.
This will trigger the zone serial number check in the slave (provided, it supports NOTIFY)
allowing the slave to verify the zone while the connection is active.
If the zone is a slave or stub zone, then the server will suppress the regular "zone up to date"
(refresh) queries and only perform them when the heartbeat-interval expires in addition to
sending NOTIFY requests.
Finer control can be achieved by using
notify which only sends NOTIFY messages,
notify-passive which sends NOTIFY messages and suppresses the normal refresh
queries, refresh which suppresses normal refresh processing and sends refresh queries
when the heartbeat-interval expires and
passive which just disables normal refresh pro-
cessing.
minimal-responses
If "yes", then the server will only add records to the authority when generating responses
and additional data sections when they are required (e.g. delegations, negative responses).
This may improve the performance of the server. Default is "no".
notify If "yes" (the default), DNS NOTIFY messages are sent when a zone for which the server is
authoritative, changes. The messages are sent to the servers listed in the zone’s NS records
(except the master server identified in the SOA MNAME field), and to any servers listed in
the
also-notify option. If explicit, notify messages are sent only to servers explicitly
listed using also-notify. If "no", no notify messages are sent.
The
notify option may also be specified in the zone statement, in which case it overrides
the notify specified in the options statement. It needs to be turned off only when the
slaves crash.
recursion
If "yes", and a DNS query requests recursion, then the server will attempt to answer the
query. If recursion is off and the server does not know the answer, it will return a referral
response. The default is "yes". Note that setting recursion to "no" does not prevent clients
from getting data from the server’s cache; it only prevents new data from being cached as an
effect of client queries. Caching may still occur as an effect of the server’s internal operation,
such as NOTIFY address lookups.
HP-UX 11i Version 2: September 2004 − 10 − Hewlett-Packard Company Section 4−−185