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! 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. Commenting out category "default" indeed seems to convince Bind 9 to log normally at last. Greets, Philippe Wiede pw@megapublic.com Ashley wrote:
I discoverd (the hard way) in SuSE 7.1 the /etc/named.conf file by default does not log anything of category 'default', which is basically everything you are trying to log. Comment out the appropriate line and syslog will get bind8 messages as it should:
In /etc/named.conf: # # do not be verbose about these problems... # logging { # category default { null; }; ### comment out this line ### category lame-servers { null; }; category cname { null; }; };
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?
Michael, I'm afraid your conclusion about not having read the documentation is false. Neither did we have any problems or errors running Bind 9 with our DNS setup. The logging statement was adapted according to the Bind 9 docs. Here is the current Bind 9.1.0 conf setup (which now works when category "default" is disabled): logging { channel "moderate_watch" { file "/var/log/named.log" versions 1 size 10m; severity info; print-time yes; print-category yes; print-severity yes; }; channel "debug_watch" { file "/var/log/named.log" versions 11 size 10m; severity debug; print-time yes; print-category yes; print-severity yes; }; ## category "default" { "moderate_watch"; }; category "config" { "debug_watch"; }; category "queries" { "moderate_watch"; }; category "general" { "moderate_watch"; }; category "xfer-in" { "debug_watch"; }; category "xfer-out" { "debug_watch"; }; category "database" { "debug_watch"; }; category "security" { "debug_watch"; }; category "notify" { "debug_watch"; }; category "network" { "debug_watch"; }; category "update" { "debug_watch"; }; category "resolver" { "debug_watch"; }; }; options { directory "/etc/dnsdata"; check-names master fail; check-names slave warn; allow-transfer { xxx.xxx.xxx.xxx; }; allow-query { any; }; recursion yes; lame-ttl 1800; pid-file "/var/run/named.pid"; statistics-file "/var/log/named.stats"; dump-file "/var/log/named_dump.db"; datasize default; stacksize default; coresize default; files unlimited; }; Philippe Wiede pw@megapublic.com Michael Roehrkasten wrote:
Hello,
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.
I compiled Bind 9.1.1 by myself and can´t see this truncating.
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??
Hi Philippe, On Wed, 4 Apr 2001, Philippe Wiede wrote:
Michael,
I'm afraid your conclusion about not having read the documentation is false. Neither did we have any problems or errors running Bind 9 with our DNS setup. The logging statement was adapted according to the Bind 9 docs. Here is the current Bind 9.1.0 conf setup (which now works when category "default" is disabled): [...]
Then I have to apologize! I just take a look into the "CHANGES" for BIND 9.1.1 Maybe this is what you mentioned? --- 9.1.1rc4 released --- 755. [bug] Fix incorrectly formatted log messages in zone.c. And here are my settings for "default": logging { channel default_syslog { syslog user; severity info; }; [...] channel moderate_debug { file "/var/log/dns.log"; severity debug 1; print-time yes; print-category yes; print-severity yes; }; [...] category default { default_syslog; moderate_debug; }; }; ------ And these settings are running pretty well. The only Logging I am missing is "xfer-out", but this seems not be implemented yet to the source code... Cheers, Michael -- Windows is not the answer, it's the question. The answer is "NO".
participants (2)
-
Michael Roehrkasten
-
Philippe Wiede