Description of problem: Excessive logging of common DNS events clogs syslog Version-Release number of selected component (if applicable): bind-9.7.0-10.P2.fc13.x86_64 How reproducible: Every time Steps to Reproduce: 1. Default installation 2. 3. Actual results: Thousands of resolver, lame-server, and edns-disabled messages clog syslog, without contributing useful information. Expected results: Only infrequent important messages should go to syslog. Additional info: Default behavior of named should change. Given the current state of the DNS ecosystem, messages in categories resolver, lame-server, edns-disabled, and queries should simply be discarded. Routine messages should go to the default_debug channel, and only potentially actionable messages should go to the default_syslog channel. Please adjust the default /etc/named.conf to use (or include) more practical logging specification, something like the following: logging { // Channels default_syslog, default_debug, default_stderr, and null // should be predefined, but adjust default_debug here channel default_debug { file "data/named.run"; severity dynamic; print-time yes; print-category yes; print-severity no; }; category default { default_syslog; }; category general { default_syslog; }; category database { default_debug; }; category security { default_syslog; }; category config { default_syslog; }; category resolver { null; }; category xfer-in { default_syslog; }; category xfer-out { default_syslog; }; category notify { default_debug; }; category client { default_debug; }; category unmatched { default_debug; }; category network { default_debug; }; category update { default_syslog; }; category update-security { default_syslog; }; category queries { null; }; category query-errors { default_debug; }; category dispatch { default_debug; }; category dnssec { default_debug; }; category lame-servers { null; }; category delegation-only { default_debug; }; category edns-disabled { null; }; };
*** Bug 607906 has been marked as a duplicate of this bug. ***
Which category do those "dns format errors" belong to?
(In reply to comment #2) > Which category do those "dns format errors" belong to? Errors written in bug #607906 belongs to "resolver" category.
bind-9.7.3-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/bind-9.7.3-1.fc14
bind-9.7.3-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/bind-9.7.3-1.fc15
bind-9.7.3-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/bind-9.7.3-1.fc13
bind-9.7.3-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bind'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bind-9.7.3-1.fc14
bind-9.7.3-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
bind-9.7.3-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
bind-9.7.3-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.