Configuring and Managing MPE/iX Internet Services (MPE/iX 6.5)

Appendix B 201
BIND 8 Configuration File
* they all end up here. also, if you
* don’t specify any channels for a
* category, the default category is
used
* instead.
* config high-level configuration file
* processing
* parser low-level configuration file
processing
* queries what used to be called “query
logging”
* lame-servers messages like “Lame server on ...”
* statistics
* panic if the server has to shut itself
* down due to an internal problem, it
* logs the problem here (as well as
* in the problem’s native category)
* update dynamic update
* ncache negative caching
* xfer-in zone transfers we’re receiving
* xfer-out zone transfers we’re sending
* db all database operations
* eventlib debugging info from the event system
* (see below)
* packet dumps of packets received and sent
* (see below)
* notify the NOTIFY protocol
* cname messages like “XX points to a CNAME”
* security approved/unapproved requests
* os operating system problems
* insist consistency check failures
* maintenance periodic maintenance
* load zone loading
* response-checks messages like
* “Malformed response ...”
* “wrong ans. name ...”
* “unrelated additional info ...”
* “invalid RR type ...”
* “bad referral ...”
*/
category parser {
syslog_errors; // you can log to as many channels
default_syslog; // as you want
};
category lame-servers { null; }; // don’t log these at all
channel moderate_debug {
severity debug 3; // level 3 debugging to file
file “foo”; // foo
print-time yes; // timestamp log entries
print-category yes; // print category name
print-severity yes; // print severity level