BIND logging issues - doesn't seem to want to log
Hey all,
I wasn't sure if this should go into the networking forum, but the issue isn't with the DNS aspect of BIND but more in trying to figure out why it won't write a logfile.
We are using BIND 9.2.4 and we are trying to configure logging so that we can determine what machines are still querying against that particular DNS server, as we would like to retire it. Here is the logging part which is at the end of the named.conf before the rndc.key include:
logging{
channel simple_log {
file "bind.log" versions 3 size 5m;
severity dynamic;
print-time yes;
print-severity yes;
print-category yes;
};
category queries {
simple_log;
};
};
I'm fairly certain that location in the log file doesn't matter, as I believe it parses the entire conf before enacting the logging. The logging config above was mainly copied from some sample configs I found online and then modified to the best of my understanding. As you may see, my understanding of the log config is fairly limited right now, so it could be an obvious mistake to the seasoned BIND pro.
Is there any reason why the above config would produce no bind.log file? Any thoughts on how to troubleshoot this? I tried running it in the foreground with the following command "named -g", which seemed to get me the closest to seeing a log from BIND as I've been able to...unfortunately I get a "not listening on any interfaces" error when I run it that way, and is proven when I try to query against it with nslookup. NSlookup works great when I start the program as a service.
Thanks for any help with this.
|