Description of problem: BIND 9.3 shipping with EL5 doesn't support NSEC3 and a number of other needed features. As EL5 will be around for some time in production, and EL6 is still forthcoming, BIND9.6 is needed for NSEC3 support. Specifically in the .GOV gTLD and others. A tech preview of BIND 9.6 is requested for EL5. Please reference: https://bugzilla.redhat.com/show_bug.cgi?id=504794 https://bugzilla.redhat.com/show_bug.cgi?id=491655
BIND 9.7 has been already released so I prefer to use it instead of older 9.6.
Wonderful. Does another bug request need to be opened, or can this just be modified to ask for a tech preview of BIND 9.7?
Just adding another vote that this be done soon. Is there a way to increase the priority?
(In reply to comment #3) > Just adding another vote that this be done soon. Is there a way to increase > the priority? You can open a ticket in the issue tracker. I think this is only one possible way how to increase the priority of this request.
Best way to increase the priority is to contact product support directly - as bugzilla is not support tool. Please inform them there is already existing bugzilla which requests that. Other way is to handle it via EPEL - this extra packages for rhel channel is maintained primarily by community and many things (e.g. git) for RHEL-5 are available there. There is no support for it - though.
I created RHEL 5.6 test package of BIND 9.7.0-P2, it is located on http://people.redhat.com/atkac/bind/5.6-test/. Note this is not an official package, yet. You will also hit problems with SELinux so you have to run this package in permissive mode.
=> VERIFIED
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 new bind97 packages add support for the new DNSSEC algorithms (NSEC3, RSA-SHA2) and for HMAC-SHA2 TSIGs (Transaction SIGnatures).
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/RHEA-2011-0035.html