[an error occurred while processing this directive]

HP OpenVMS Systems Documentation
Content starts here >

Compaq TCP/IP Services for OpenVMS
Release Notes

Previous Contents
C.5.3.6.13 Tuning Options

Table C-15 describes the options provided for tuning the BIND server.

Table C-15 Tuning Options
Options Description
lame-ttl Sets the number of seconds to cache a lame server indication. A value of zero disables caching. (This is not recommended.) The default is 600 (10 minutes); the maximum value is 1800 (30 minutes).
max-ncache-ttl To reduce network traffic and increase performance, the server stores negative answers. The max-ncache-ttl option is used to set a maximum retention time for these answers in the server in seconds. The default is 10800 seconds (3 hours). The value of max-ncache-ttl cannot exceed 7 days and is silently truncated to 7 days if set to a greater value.
max-cache-ttl Sets the maximum time for which the server caches ordinary (positive) answers. The default is one week (7 days).
min-roots The minimum number of root servers that is required for a request for the root servers to be accepted. The default is 2.

This option is not yet implemented.

sig-validity-interval Specifies the number of days into the future when DNSSEC signatures automatically generated as a result of dynamic updates will expire. (See Section C.5.7 for more information.) The default is 30 days. The signature inception time is unconditionally set to one hour before the current time to allow for a limited amount of clock skew.
min-refresh-time
max-refresh-time
min-retry-time
max-retry-time 		Controls the server's behavior when refreshing a zone (querying for SOA changes) or when retrying failed transfers. Usually the SOA values for the zone are used, but these values are set by the master, giving slave server administrators little control over their contents.

These options allow the administrator to set a minimum and maximum refresh and retry time on a per-zone, per-view, or per-server basis. These options are valid for master, slave, and stub zones, and they set the SOA refresh and retry times to the specified values.

C.5.3.6.14 The Statistics File

The statistics file generated by BIND 9 is similar, but not identical, to that generated by BIND 8.

The statistics dump begins with the following line: 


+++ Statistics Dump +++ (973798949)

The number in parentheses is a standard UNIX time stamp, measured as seconds since January 1, 1970. Following that line are a series of lines containing a counter type, the value of the counter, a zone name (optional), and a view name (optional). The lines without view and zone listed are global statistics for the entire server. Lines with a zone and view name apply to the given view and zone (the view name is omitted for the default view). The statistics dump ends with the following line: 


--- Statistics Dump --- (973798949)

The time stamp is identical to the one in the beginning line.

Table C-16 describes the statistics counters that are maintained.

Table C-16 Statistics Counters
Counter Description
success The number of successful queries made to the server or zone. A successful query is defined as query that returns a NOERROR response other than a referral response.
referral The number of queries that resulted in referral responses.
nxrrset The number of queries that resulted in NOERROR responses with no data.
nxdomain The number of queries that resulted in NXDOMAIN responses.
recursion The number of queries that caused the server to perform recursion in order to find the final answer.
failure The number of queries that resulted in a failure response other than those described in the preceding counters.

C.5.3.7 The SERVER Statement

The server statement defines characteristics to be associated with a remote name server. The server statement has the following syntax: 


server ip_addr { 
    [ bogus yes_or_no ; ] 
    [ provide-ixfr yes_or_no ; ] 
    [ request-ixfr yes_or_no ; ] 
    [ edns yes_or_no ; ] 
    [ transfers number ; ] 
    [ transfer-format ( one-answer | many-answers ) ; ]] 
    [ keys { string ; [ string ; [...]] } ; ] 
};

The server statement can occur at the top level of the configuration file or inside a view statement. If a view statement contains one or more server statements, only those apply to the view, and any top-level ones are ignored. If a view contains no server statements, any top-level server statements are used as defaults.

Table C-17 describes the clauses in the server statement.

Table C-17 Server Statement Clauses
Clause Description
bogus If you discover that a remote server is giving out bad data, marking it as bogus prevents further queries to it. The default value of bogus is NO.
provide-ixfr Determines whether the local server, acting as master, responds with an incremental zone transfer when the given remote server, a slave, requests it. If this option is set to YES, incremental transfer is provided whenever possible. If set to NO, all transfers to the remote server are nonincremental. If not set, the value of the provide-ixfr option in the global options statement is used as a default.
request-ixfr Determines whether the local server, acting as a slave, requests incremental zone transfers from the given remote server, a master. If this option is not set, the value of the request-ixfr option in the global options statement is used as a default.

IXFR requests to servers that do not support IXFR automatically falls back to AXFR. Therefore, you do not need to list manually which servers support IXFR and which ones do not; the global default of YES should always work. The purpose of the provide-ixfr and request-ixfr clauses is to make it possible to disable the use of IXFR, even when both master and slave claim to support it; for example, if one of the servers crashes or corrupts data when IXFR is used. See Section C.5.6 for more information.