Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1115294 - [RFE] Add support for DNSSEC
Summary: [RFE] Add support for DNSSEC
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: Namita Soman
Marc Muehlfeld
URL:
Whiteboard:
Depends On: 829395 1044159 1044170 1044171 1061212 1097749 1097753 1117157 1117174 1119738 1121658 1122495 1193892 1196971 1204100 1261530
Blocks: 1181710 1249775 1664718
TreeView+ depends on / blocked
 
Reported: 2014-07-02 07:12 UTC by Martin Kosek
Modified: 2019-05-21 10:22 UTC (History)
12 users (show)

Fixed In Version: ipa-4.2.0-1.el7
Doc Type: Technology Preview
Doc Text:
.DNSSEC available as Technology Preview in IdM Identity Management (IdM) servers with integrated DNS now support DNS Security Extensions (DNSSEC), a set of extensions to DNS that enhance security of the DNS protocol. DNS zones hosted on IdM servers can be automatically signed using DNSSEC. The cryptographic keys are automatically generated and rotated. Users who decide to secure their DNS zones with DNSSEC are advised to read and follow these documents: * link:http://tools.ietf.org/html/rfc6781#section-2[DNSSEC Operational Practices, Version 2] * link:http://dx.doi.org/10.6028/NIST.SP.800-81-2[Secure Domain Name System (DNS) Deployment Guide] * link:http://tools.ietf.org/html/rfc7583[DNSSEC Key Rollover Timing Considerations] Note that IdM servers with integrated DNS use DNSSEC to validate DNS answers obtained from other DNS servers. This might affect the availability of DNS zones that are not configured in accordance with recommended naming practices described in the link:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices[Red Hat Enterprise Linux Networking Guide].
Clone Of:
: 1249775 1664718 (view as bug list)
Environment:
Last Closed: 2015-11-19 12:00:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2362 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2015-11-19 10:40:46 UTC

Description Martin Kosek 2014-07-02 07:12:34 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3801

bind-dyndb-ldap in Fedora 20 plans to introduce DNSSEC support. Add support to FreeIPA as well.

Related bind-dyndb-ldap ticket: https://fedorahosted.org/bind-dyndb-ldap/ticket/56

Related bind-dyndb-ldap design documents:
* https://fedorahosted.org/bind-dyndb-ldap/wiki/BIND9/Design/DNSSEC
* https://fedorahosted.org/bind-dyndb-ldap/wiki/BIND9/Design/RBTDB

Related discussion on freeipa-devel: http://www.redhat.com/archives/freeipa-devel/2013-May/msg00177.html

Major challenges in FreeIPA will be a secure synchronization of DNSSEC keys which need to be available to all FreeIPA masters with DNS support. There also should be a possibility to rotate the keys.

Comment 1 Jenny Severance 2014-07-03 14:25:14 UTC
Can you please close this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=829395

Comment 2 Martin Kosek 2014-07-04 08:03:52 UTC
I am not sure I want to do that. DNSSEC support in IPA has different scope that DNSSEC support in bind-dyndb-ldap component. It also needs to publish proper interface + secure key exchange for multi-master environment.

Comment 3 Petr Spacek 2014-07-18 12:21:27 UTC
I'm adding DS bugs which hammers performance in cases where SyncRepl is used. (SyncRepl is a requirement for bind-dyndb-ldap version which supports DNSSEC.)

Comment 4 Petr Spacek 2014-07-18 12:23:59 UTC
And also we need SyncRepl support itself.

Comment 7 Martin Kosek 2014-08-19 08:45:04 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4462

Comment 8 Martin Kosek 2014-10-21 10:32:25 UTC
Initial upstream support (#3801) was fixed upstream, it will be part of FreeIPA 4.1. See details in

https://fedorahosted.org/freeipa/ticket/3801

Comment 9 Martin Kosek 2014-10-24 14:28:16 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4657

Comment 10 Martin Kosek 2014-10-24 14:28:33 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4658

Comment 11 Petr Viktorin 2014-10-29 14:04:51 UTC
Improvements/fixes are being applied upstream, see https://fedorahosted.org/freeipa/ticket/4657 for details.

Comment 13 Petr Spacek 2014-11-14 19:34:21 UTC
Adding dependencies client side: These changes on clients make the feature actually useful.

IMHO we should consider implementing https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver in RHEL too.

Comment 15 Petr Vobornik 2015-03-06 14:49:32 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4933

Comment 29 Martin Kosek 2015-07-07 08:12:32 UTC
FreeIPA ticket 4462 will not be part of this feature, this part was not done upstream.

Comment 30 Martin Kosek 2015-07-07 08:15:39 UTC
The intended functionality is finished upstream, the feature is now maintenance mode. I am thus moving this RFE to POST.

Comment 35 Petr Spacek 2015-08-26 11:19:52 UTC
Here is more descriptive text for release notes.

Comment 36 Kaleem 2015-09-23 12:56:36 UTC
Verified.

IPA/bind* rpm version:
======================
[root@dhcp207-229 ~]# rpm -q ipa-server bind bind-pkcs11 bind-dyndb-ldap opendnssec
ipa-server-4.2.0-11.el7.x86_64
bind-9.9.4-29.el7.x86_64
bind-pkcs11-9.9.4-29.el7.x86_64
bind-dyndb-ldap-8.0-1.el7.x86_64
opendnssec-1.4.7-3.el7.x86_64
[root@dhcp207-229 ~]#

Done verification of this RFE by execution of following test cases.
-------------------------------------------------------------------
1. Installation of DNSSEC component with a lot of combinations with forwarders(DNSSEC enabled/disabled, DNS component not installed etc), installation of dnssec component after upgrade to RHEL-7.2 .
2. Migration of DNSSEC component to another IPA replica .
3. DNSzone/DNSrecord signing with verification of dnssec chain of trust, enabling/disabling of signing on dnszone .
4. DNSForward zone addition where DNSSEC enabled/disabled.

Comment 38 Petr Spacek 2015-10-22 06:59:29 UTC
I've added following link to the doc text:

DNSSEC Key Rollover Timing Considerations:
http://tools.ietf.org/html/rfc7583

Comment 40 errata-xmlrpc 2015-11-19 12:00:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2362.html


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