BIND 9.2.0 Release Notes for HP-UX 11i v1

New and Changed Features
New BIND 9.2.0 Features
Chapter 18
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:
[ coresize size_spec ; ]
• 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 Option in “Server” Statement
The bogus option can be used to prevent queries to a remote server which is giving
out invalid data. The default value of bogus is no. The syntax of bogus option in
the “Server” statement is as shown below: