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

n
named.conf(4) named.conf(4)
(BIND 9.3)
max-transfer-idle-out
Outbound zone transfers making no progress in this many minutes will be terminated. The
default is 60 minutes (1 hour). The maximum value is 28 days (40320 minutes).
max-transfer-time-in
Inbound zone transfers running longer than this many minutes will be terminated. The
default is 120 minutes (2 hours). The maximum value is 28 days (40320 minutes).
max-transfer-time-out
Outbound zone transfers running longer than this many minutes will be terminated. The
default is 120 minutes (2 hours). The maximum value is 28 days (40320 minutes).
notify-source
Determines which local source address, and optionally UDP port, will be used to send
NOTIFY messages. This address must appear in the slave server’s
masters zone clause
or in an
allow-notify clause. This statement sets the
notify-source for all zones,
but can be overridden on a per-zone or per-view basis by including a
notify-source
statement within the zone or view statement in the configuration file.
notify-source-v6
The same as notify-source
, but applies to NOTIFY messages sent to IPv6 addresses.
serial-query-rate
Slave servers will periodically query master servers to find out if zone serial numbers have
changed. Each such query uses a minute amount of the slave server’s network bandwidth.
To limit the amount of bandwidth used, BIND 9.3 limits the rate at which queries are sent.
The value of the
serial-query-rate
option, an integer, is the maximum number of
queries sent per second. The default is 20.
transfer-format
Zone transfers can be sent using two different formats, one-answer and many-
answers
. The transfer-format
option is used on the master server to determine
which format it sends.
one-answer uses one DNS message per resource record
transferred. many-answers packs as many resource records as possible into a message.
many-answers is more efficient, but is only supported by relatively new slave servers,
such as BIND 9.3, BIND 8.x, and patched versions of BIND 4.9.x. The default is many-
answers
. transfer-format
may be overridden on a per-server basis by using the
server statement.
transfer-source
Determines which local address will be bound to IPv4 TCP connections used to fetch zones
transferred inbound by the server. It also determines the source IPv4 address, and option-
ally the UDP port, used for the refresh queries and forwarded dynamic updates. If not set,
it defaults to a system-controlled value which will usually be the address of the interface
"closest to" the remote end. This address must appear in the remote end’s
allow-
transfer
option for the zone being transferred, if one is specified. This statement sets
the transfer-source for all zones, but can be overridden on a per-view or per-zone
basis by including a
transfer-source
statement within the view or zone block in
the configuration file.
transfer-source-v6
The same as transfer-source, except that zone transfers are performed using IPv6.
transfers-in
The maximum number of concurrently running inbound zone transfers. The default value
is 10. The maximum value is 28 days (40320 minutes). Increasing
transfers-in may
speed up the convergence of slave zones, but it may also increase the load on the local sys-
tem.
transfers-out
The maximum number of concurrently running outbound zone transfers. Zone transfer
requests in excess of the limit will be refused. The default value is 10.
transfers-per-ns
The maximum number of concurrently running inbound zone transfers from a given remote
name server. The default value is 2. Increasing transfers-per-ns may speed up the
convergence of slave zones, but it also may increase the load on the remote name server.
transfers-per-ns may be overridden on a per-server basis by using the transfers
HP-UX 11i Version 3: February 2007 − 21 − Hewlett-Packard Company 253