Created attachment 731323 [details] corrected sample file /usr/share/doc/bind-9.9.2/sample/etc/named.conf Description of problem: After a while CPU load of BIND named goes over 200% and stays there, while still serving answers to DNS queries. Version-Release number of selected component (if applicable): 9.9.2-8.P1.fc18.x86_64 How reproducible: Start it up, and just wait for a couple of hours, or one or two days :-) Note: this was on a very lightly used system. Restarting the daemon won't help; the daemon runs normal again for a while only after rebooting. Additional info: This problem appears to be triggered by a missing statement: managed-keys-directory "dynamic"; in the /etc/named.conf file. This problem was already reported in bug #709205 for BIND named 9.7.4 on FC14 here: https://bugzilla.redhat.com/show_bug.cgi?id=709205 Yes, the managed-keys-directory statement is there in the basic named.conf that is installed with the package. However, it is missing in the template configuration file /usr/share/doc/bind-9.8.2/sample/etc/named.conf that a lot of people might be using. Attached a corrected sample file (added the DLV key path too).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fixed in bind-9.9.2-11.P2.fc18 [1]. [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=418506
bind-9.9.3-0.6.rc2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/bind-9.9.3-0.6.rc2.fc19
bind-9.9.3-0.6.rc2.fc19, dhcp-4.2.5-12.fc19, bind-dyndb-ldap-3.2-1.fc19, dnsperf-2.0.0.0-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
bind-dyndb-ldap-2.6-2.fc18,dnsperf-2.0.0.0-4.fc18,dhcp-4.2.5-12.fc18,bind-9.9.3-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bind-dyndb-ldap-2.6-2.fc18,dnsperf-2.0.0.0-4.fc18,dhcp-4.2.5-12.fc18,bind-9.9.3-2.fc18
dhcp-4.2.5-2.fc17,dnsperf-2.0.0.0-3.fc17,bind-dyndb-ldap-2.5-2.fc17,bind-9.9.3-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/dhcp-4.2.5-2.fc17,dnsperf-2.0.0.0-3.fc17,bind-dyndb-ldap-2.5-2.fc17,bind-9.9.3-2.fc17
Package dhcp-4.2.5-2.fc17, dnsperf-2.0.0.0-3.fc17, bind-dyndb-ldap-2.5-2.fc17, bind-9.9.3-3.P1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dhcp-4.2.5-2.fc17 dnsperf-2.0.0.0-3.fc17 bind-dyndb-ldap-2.5-2.fc17 bind-9.9.3-3.P1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10100/dhcp-4.2.5-2.fc17,dnsperf-2.0.0.0-3.fc17,bind-dyndb-ldap-2.5-2.fc17,bind-9.9.3-3.P1.fc17 then log in and leave karma (feedback).
bind-dyndb-ldap-2.6-2.fc18, dnsperf-2.0.0.0-4.fc18, dhcp-4.2.5-12.fc18, bind-9.9.3-3.P1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
dhcp-4.2.5-2.fc17, dnsperf-2.0.0.0-3.fc17, bind-dyndb-ldap-2.5-2.fc17, bind-9.9.3-3.P1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.