Hide Forgot
Description of problem: Update bind to the latest 9.7.X bugfix release (currently 9.7.2-P2). Bugfix release contains only bugfixes and it's good idea to rebase bind package to fix many undiscovered issues. Version-Release number of selected component (if applicable): bind-9.7.0-5.P2.el6
Yss, please rebase to latest stable.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The 9.7.2-P3 release contains more than 50 bugfixes. Important ones are: * dnssec-signzone didn't handle out of zone records well * named could return SERVFAIL for negative responses from unsigned zones * it was possible for re-signing to stop after removing a DNSKEY * NSEC3 chains could be left behind when transitioning to insecure * nsupdate didn't default to the parent zone when updating DS records * handle REVOKED keys better
Sanity and regression testing performed. Setting VERIFIED. Testing results see https://beaker.engineering.redhat.com/jobs/63067.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1,3 @@ -The 9.7.2-P3 release contains more than 50 bugfixes. Important ones are: +the bind packages in this update are rebased to version 9.7.2-P3. Full details of the bugfixes and enhancements supplied by this rebase are available in the bind release notes linked to in the References section of this errata. -* dnssec-signzone didn't handle out of zone records well + -* named could return SERVFAIL for negative responses from unsigned zones +http://ftp.isc.org/isc/bind9/9.7.3/RELEASE-NOTES-BIND-9.7.3.html-* it was possible for re-signing to stop after removing a DNSKEY -* NSEC3 chains could be left behind when transitioning to insecure -* nsupdate didn't default to the parent zone when updating DS records -* handle REVOKED keys better
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0541.html