Logging problem
Doug Barton
dougb at dougbarton.us
Mon Aug 10 03:44:48 UTC 2009
Raven wrote:
> Hi all.
> I have just deployed a bind installation (freebsd port v9.4.3-P2)
The port was updated to 9.4.3-P3 the same day it was released. That
version contains an important bug fix that you want. Please update
your ports tree and install the new version.
> and I
> seem to be unable to have it log the queries.
> This is the section I put in named.conf:
>
> logging {
> channel munin_log {
> file "/var/log/bind9/query.log" versions 7 size 100m;
> severity dynamic;
I agree with Mark that you don't want this. If all you're trying to
catch is queries you don't need to specify the severity at all.
> print-time yes; };
>
> category queries {
> munin_log; };
> };
>
>
> What's weird is that if I start bind from the cli with
> "named -f -c /etc/namedb/named.conf -d 3"
> then the queries are correctly logged to the desired file.
So I assume that when the logging is not working that you're using the
rc.d script? If you're not, you should be. That script runs named in a
chroot directory by default, and makes sure that all the necessary
subdirectories are created and have the right permissions. Make sure
you add:
named_enable=yes
named_program=/usr/local/sbin/named
to your /etc/rc.conf[.local] and then do '/etc/rc.d/named start' and
you should be fine.
Good luck,
Doug
More information about the bind-users
mailing list