Configuring and Managing MPE/iX Internet Services (August 2002)

Appendix C
BIND 8.1 Enhanced Features
BIND 8 Highlights
233
Query Address
If the server doesn’t know the answer to a question, it will query other nameservers. query-source specifies
the address and port used for such queries. If address is * or is omitted, a wildcard IP address (INADDR_ANY)
will be used. If port is * or is omitted, a random unprivileged port will be used. The default is
query-source address * port *;
NOTE Query-source currently applies only to UDP queries; TCP queries always use a wildcard IP
address and a random unprivileged port.
Zone Transfers
max-transfer-time-in Inbound zone transfers (named-xfer processes) running longer than this
many minutes will be terminated. The default is 120 minutes (2 hours).
transfer-format The server supports two zone transfer methods. 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 known to be understood by BIND 8.1 and patched
versions of BIND 4.9.5. The default is one-answer. transfer-format
may be overridden on a per-server basis by using the server statement.
transfers-in The maximum number of inbound zone transfers that can be running
concurrently. The default value is 10. Increasing transfers-in may speed
up the convergence of slave zones, but it also may increase the load on the
local system.
transfers-out This option will be used in the future to limit the number of concurrent
outbound zone transfers. It is checked for syntax, but is otherwise ignored.
transfers-per-ns The maximum number of inbound zone transfers (named-xfer processes)
that can be concurrently transferring from a given remote nameserver.
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
nameserver. transfers-per-ns may be overridden on a per-server
basis by using the transfers phrase of the server statement.
Resource Limits
The server’s usage of many system resources can be limited. Some operating systems don’t support some of
the limits. On such systems, a warning will be issued if the unsupported limit is used. Some operating
systems don’t support limiting resources, and on these systems a cannot set resource limits on this system
message will be logged.
Scaled values are allowed when specifying resource limits. For example, 1G can be used instead of
1073741824 to specify a limit of one gigabyte. unlimited requests unlimited use, or the maximum available
amount. default uses the limit that was in force when the server was started. See size_spec for more details.
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.
files The maximum number of files the server may have open concurrently. The default is
unlimited.