BIND 8.1.2 Release Notes

New and Changed Features
New Features
Chapter 112
An example key statement is:
key sample_key{ algorithm hmac-md5;
secret "secret here";};
You can use the key ID defined in the key statement to associate an
authentication method with a particular name server. You must create a
key ID in the key statement before using it in a server definition.
The logging Statement
The logging statement specifies what messages the server logs and
where the log messages are sent. The logging statement also configures
various logging options for the name server.
The logging statement configures the logging system, which sends
messages to one or more channels. A channel describes a destination: a
file, syslog, or the bit bucket. A channel associates output methods,
format options and severity levels with a name. You can use this name to
select how various categories of messages are logged.
Channels perform the following tasks:
• Limit incoming messages to a given severity level.
• Limit the size of the logging file.
• Manage multiple versions of the logging file (to maintain historic
data).
• Direct the logging messages to any of the syslog facilities.
There are several default channels, and you can define more channels in
the logging statement in the configuration file. Note that, you can use
only one logging statement to define many channels and categories. If
there are multiple logging statements in a configuration file, the first
defined statement determines the logging configuration, and warnings
are issued for others.
Message Severity Levels
The severity levels include all the syslog severities as well as the
multiple debug levels. These levels correspond to the different debugging
levels in named (the BIND 8.x daemon) and are ranked so that the higher
levels are less severe. If you configure a channel for debug level 3, in
addition to level 3 it accepts and logs messages at levels 2 and 1.
The default channels are as follows: