You need to determine which logging category a particular message is in.
With a BIND 9 name server, add a channel substatement to the logging statement in named.conf, redefining the default_syslog channel so that the name server prints the category of all messages. For example:
logging { channel default_syslog { syslog daemon; // usually the default print-category yes; }; };
Then wait for the message in question to reappear, or induce the name server to log it again. The name server will print the category of the message just before the message itself. For example:
Jun 26 16:31:56 ns1 named[62314]: general: loading configuration from /etc/named.conf
This shows that this message is in the general category.
BIND 8 name servers won let you redefine the default_syslog channel, so define a new syslog channel and assign the default category of messages to it:
logging { channel new_syslog { syslog daemon; print-category yes; }; category default { new_syslog; }; };
You can use the same technique to find out the severity a given message is logged at; just use the print-severity substatement instead of print-category.
"The Logging Statement" in Chapter 7 of DNS and BIND.
Getting Started
Zone Data
BIND Name Server Configuration
Electronic Mail
BIND Name Server Operations
Delegation and Registration
Security
Interoperability and Upgrading
Resolvers and Programming
Logging and Troubleshooting
IPv6