Installing and Administering Internet Services

92 Chapter3
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
Example logging Statement
This section provides an example log configuration. The default for most
categories is default_syslog and default_debug.
logging{
Channel lame {
File lame-servers.log;
Size 10M; Severity info;
};
channel log { syslog local0;};
category lame-server {lame;};
category default {log;};
};
Channels and Channel Messages
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. This name can be used to select how various categories of
messages are logged.
A channel can do the following:
• limit incoming messages to a given severity level.
• place a limit on 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. Not that only one logging
statement is used to define as many channels and categories as you
want. If there are multiple logging statements in a configuration, the
first defined statement determines the logging configuration and
warnings are issued for the others.
Message Severity Levels The severity levels include all the syslog
severities as well as multiple debug levels. These levels correspond to the
different debugging levels present in named (the BIND 8.x daemon) and
are ranked so that higher levels are less severe. Thus, a channel can be
configured for debug level 3, and it will also accept and log messages at
levels 2 and 1.