Hello, On Wed, 4 Apr 2001, Philippe Wiede wrote:
Thanks Ashley for your discovery!
I also had trouble getting any version of Bind 9 to log as it used to log in previous versions (using common logging statements in named.conf). Missing any user reports in corresponding newsgroups I thought I was the only one with this problem!
Maybe they compiled Bind 9 themself and have had the time to read: /usr/local/src/bind-9.1.1/doc/misc/migration --- 1.3. Logging [...] Another difference is that the "logging" statement only takes effect after the entire named.conf file has been read. This means that when the server starts up, any messages about errors in the configuration file are always logged to the default destination (syslog) when the server first starts up, regardless of the contents of the "logging" statement. In BIND 8, the new logging configuration took effect immediately after the "logging" statement was read.
It seems to me that this is a bug in bind 9.xx. Between named restarts, either it logs nothing at all, or only logs lame dns entries, or only logs queries, but always without a trace of logic. And to all of above, Bind 9 truncates its log file each time after each reload.
I compiled Bind 9.1.1 by myself and can´t see this truncating.
Commenting out category "default" indeed seems to convince Bind 9 to log normally at last.
Maybe this above logging-difference is that what you call "bug"? Cheers Michael -- If Windows is the solution, can we please have the problem back?