Bug 695382 - bind97 doesn't contain root zone DNSKEY
Summary: bind97 doesn't contain root zone DNSKEY
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: bind97
Version: 5.6
Hardware: Unspecified
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact:
URL:
Whiteboard:
Depends On: 693788
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 14:35 UTC by RHEL Program Management
Modified: 2012-07-27 14:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, bind97 did not contain the root zone DNSKEY. DNSKEY is now located in /etc/named.root.key.
Clone Of:
Environment:
Last Closed: 2011-05-12 12:30:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0510 0 normal SHIPPED_LIVE bind97 bug fix and enhancement update 2011-05-12 12:30:33 UTC

Description RHEL Program Management 2011-04-11 14:35:09 UTC
This bug has been copied from bug #693788 and has been proposed
to be backported to 5.6 z-stream (EUS).

Comment 4 Adam Tkac 2011-04-12 08:04:11 UTC
Fixed in bind97-9.7.0-6.P2.el5_6.1.

Comment 6 Eva Kopalova 2011-04-20 16:06:44 UTC
    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:
Previously, bind97 did not contain the root zone DNSKEY. DNSKEY is now located in /etc/named.root.key.

Comment 8 errata-xmlrpc 2011-05-12 12:30:43 UTC
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-0510.html


Note You need to log in before you can comment on or make changes to this bug.