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

n
named.conf(4) named.conf(4)
requests in excess of the limit will be refused. Default value is 10.
transfers-per-ns
The maximum number of concurrently running inbound zone transfers from a given remote
nameserver. Default value is 2. Increasing transfers-per-ns
may speed up the conver-
gence of slave zones, but it also may increase the load on the remote nameserver.
transfers-per-ns
may be overridden on a per-server basis by using the
transfers
phrase of the server statement.
transfer-source
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 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.
notify-source
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/per-view basis by including a
notify-
source statement within the zone or view block in the configuration file.
notify-source-v6
The same as notify-source, but applies to notify messages sent to IPv6 addresses.
Operating System Resource Limits
The server’s usage of many system resources can be limited. Scaled values are allowed when specifying
resource limits. For example, 1G can be used instead of 1073741824 to specify a limit of one gigabyte.
An "unlimited_size_spec" requests unlimited use, or the maximum available amount. The default uses
the limit that was in force when the server was started.
The following options set operating system resource limits for the name server process. A warning will be
issued if the unsupported limit is used.
coresize The maximum size of a core dump. The default is default.
datasize The maximum amount of data memory the server may use. The default is default.
This is a hard limit on server memory usage. If the server attempts to allocate memory
in excess of this limit, the allocation will fail, which may in turn leave the server unable
to perform DNS service. Therefore, this option is rarely useful as a way of limiting the
amount of memory used by the server, but it can be used to raise an operating system
data size limit that is too small by default. If you wish to limit the amount of memory
used by the server, use the max-cache-size and recursive-clients
options
instead.
files The maximum number of files the server may have open concurrently. Default is unlim-
ited.
stacksize The maximum amount of stack memory the server may use. The default is default.
Server Resource Limits
The following options set limits on the server’s resource consumption that are enforced internally by the
server rather than the operating system.
recursive-clients
The maximum number of simultaneous recursive lookups the server will perform on behalf of
clients. The default is 1000. Because each recursing client uses a fair bit of memory, on the
order of 20 kilobytes, the value of the recursive-clients option may have to be
decreased on hosts with limited memory.
HP-UX 11i Version 2: September 2004 − 14 − Hewlett-Packard Company Section 4−−189