Why isn't my logging statement working?

Answered Wed, 24 Apr 2002

> I am running BIND 8.2.5 on Solaris 2.7. I can not get bind logging to work
> We are getting loads of denied update messages in syslog so I want to log
> these messages to another file. I added the following to the top of
> named.conf
>
> logging {
>
> channel dns_file {
> file "/var/adm/dns.log" versions 16 size 10m;
> severity error;
> print-category yes;
> print-severity yes;
>
> };
>
> category default { dns_file; default_syslog; };
> category panic { dns_file; default_syslog; };
> category packet { dns_file; };
> category eventlib { dns_file; };
> category queries { dns_file; };
> category update { dns_file; };
>
> };
>
> I am finding that it is not creating the dns.log file and messages are still
> going to syslog. I have tried removing the default_syslog from the category
> statement then no bind loggings occurs. I tried changing the name of the
> logging file in case it was too long but that made no difference. When I
> load named it does complain about any errors in named.conf. I do not know
> why it is not working and do not know what to try next.

"Update denied" messages are in the security category, and you haven't
sent the security category to dns_file.

Moreover, many interesting messages are below the severity error. If
you want to see more messages, change the severity in dns_file to info,
notice or warning.

cricket