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

n
named.conf(4) named.conf(4)
(BIND 9.3)
Query Address Options
If the server is unable to answer a question, it will query other name servers.
query-source
Specifies the address and port used for such queries.
query-source-v6
Specifies the address and port used for queries sent over IPv6.
If address is * or is omitted, a wildcard IP address (
INADDR_ANY ) is used. If port is * or is omitted, a
random unprivileged port will be used. The default address and port are:
query-source address * port * ;
query-source-v6 address * port * ;
Note: The address specified in the
query-source option is used for both UDP and TCP queries, but the
port applies only to UDP queries. TCP queries always use a random unprivileged port.
RRset Ordering Option
When multiple records are returned in an answer, it may be useful to configure the order of the records
placed into the response.
The
rrset-order option permits the configuration of the ordering of the records in a multiple record
response.
order_spec is defined as:
[ class class_name ][type type_name ][name "domain_name" ]
order ordering
If no class is specified, the default is ANY.Ifnotype is specified, the default is
ANY.Ifnoname
is specified, the default is *.
The values for ordering are:
fixed Records are returned in the order they are defined in the zone file.
random Records are returned in some random order.
cyclic Records are returned in a round-robin order.
In this example, any responses for type A records in class IN that have host.example.com
as a suffix,
are always returned in
random order. All other records are returned in cyclic order.
rrset-order {
class IN type A name "host.example.com" order random;
order cyclic;
};
If multiple rrset-order statements appear, they are not combined; the last one applies.
Server Resource Limit Options
The following options set limits on the server’s resource consumption that are enforced internally by the
server rather than the operating system.
max-cache-size
The maximum amount of memory to use for the server’s cache, in bytes. When the amount
of data in the cache reaches this limit, the server will cause records to expire prematurely
so that the limit is not exceeded. In a server with multiple views, the limit applies
separately to the cache of each view. The default is unlimited , meaning that records
are purged from the cache only when their TTLs expire.
max-journal-size
Sets a maximum size for each journal file. When the journal file approaches the specified
size, some of the oldest transactions in the journal will be automatically removed. The
default is unlimited.
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.
250 Hewlett-Packard Company − 18 − HP-UX 11i Version 3: February 2007