Internet Services Delta Manual for HP-UX 11i Version 1.6

statstics-file "path_name";
The statistics file generated by BIND 9.2.0 is similar, but not identical, to that generated by
BIND 8.1.2. For information on the format of the statistics file and the statistics counters, refer
to the named-conf(1) man page distributed with this release.
• blackhole
This option is used to specify a list of addresses from which the server will not accept queries
or and does not use them to resolve a query. Default is none. The syntax of blackhole
option in the "options" statement in the /etc/named.conf file is as shown below:
[ blackhole {address_match_list {; ]
• coresize
This option is used to specify the maximum size of a core dump. Default is default. The
syntax of coresize option in the "Options" statement in the /etc/named.conf file is as
shown below:
[ blackhole {address_match_list {; ]
• sortlist
The sortlist statement takes an address_match_list and interprets it. Each top level
statement in sortlist must be an explicit address_match_list with one or two elements.
The first element, which may be an IP address, IP prefix, acl name or a nested
address_match_list is checked against the source address of the query until a match is found.
Once the source address of the query has been matched, if the top level statement contains
only one element, the actual element that matched the source address is used to select the
address in the response to move to the beginning of the response. Each top level statement
element is assigned a distance and the address in the response with the minimum distance is
moved to the beginning of the response.
A sample sortlist statement usage in the Options statement in the /etc/named.conf
file is as shown below:
[ sortlist { address_match_list }];
NOTE: Refer to the named.conf(4) man page for more information on the usage of
sortlist statement.
• max-cache-size
max-cache-size is used to specify 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.
New Options in "zone" Statement
The following are the new zone options added in BIND 9.2.0:
• update-policy
This is applicable only for master zones. When specified, one should ensure that allow-update
is not present, else it is an error. A set of rules are specified, where each rule either grants or
denies permissions for one or more names to be updated by one or more identities. If the
dynamic update request message is signed (that is, it includes either a TSIG or SIG(0) record),
the identity of the signer will be determined.
A rule definition looks like this:
Chapter Overview 35