named.conf.4 (2010 09)

n
named.conf(4) named.conf(4)
(BIND 9.3)
transferred. many-answers packs as many resource records as possible into a mes-
sage. 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
optionally 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 state-
ment 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 system.
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 phrase of the server statement.
use-alt-transfer-source
Use the alternate transfer sources or not. If views are specified, this defaults to
no; oth-
erwise, it defaults to
yes (for BIND 8 compatibility).
The server Statement
server Statement Grammar
server ip_addr {
[ bogus yes_or_no ; ]
[ edns yes_or_no ; ]
[ keys { string ; [ string ; ]... }; ]
[ provide-ixfr yes_or_no ; ]
[ request-ixfr yes_or_no ; ]
[ transfer-format ( one-answer | many-answers ) ; ]
[ transfer-source ( ip4_addr | * )[port ip_port ] ; ]
[ transfer-source-v6 ( ip6_addr | * )[port ip_port ] ; ]
[ transfers number ; ]
};
server Statement Definition and Usage
The
server statement defines characteristics to be associated with a remote name server. The server
statement can occur at the top level of the configuration file or inside a view statement. If a view state-
ment contains one or more server statements, only those apply to the view and any top-level ones are
ignored. If a view statement contains no server statements, any top-level server statements are
used as defaults.
bogus If you discover that a remote server is giving out bad data, marking it as bogus yes
will prevent further queries to it. The default value is bogus no.
22 Hewlett-Packard Company − 22 − HP-UX 11i Version 3: September 2010