Bug 1207541

Summary: [RFE] Generic support for unknown DNS RR types (RFC 3597)
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kosek <mkosek>
Component: bind-dyndb-ldapAssignee: Pavel Picka <ppicka>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0CC: ppicka, pspacek
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bind-dyndb-ldap-7.99-1.GIT158e95e.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 10:21:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1181710, 1211608    
Attachments:
Description Flags
Evidence of verify none

Description Martin Kosek 2015-03-31 07:02:20 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/157

= Enhancement proposal =
[[http://tools.ietf.org/html/rfc3597|RFC 3597]] describes mechanism necessary for supporting unknown/new DNS RR types in DNS servers. BIND 9 supports this so should expose this functionality too. It would be a future-proof workaround for cases when someone needs a new type.

= Use case =
Users may want to use new types which are not directly supported by underlying BIND or LDAP schema.

= Proposed implementation =
1 new attribute with sub-type specifying RR type as a number. This attribute should contain data encodedaccording to [[http://tools.ietf.org/html/rfc3597#section-5|RFC 3597 section 5]].

Design discussion:
https://www.redhat.com/archives/freeipa-devel/2015-March/msg00176.html

Comment 4 Petr Spacek 2015-09-10 14:39:27 UTC
This bug was documented as part of rebase bug 1204110.

Comment 5 Pavel Picka 2015-09-22 12:15:35 UTC
Created attachment 1075796 [details]
Evidence of verify

VERIFIED

Comment 7 errata-xmlrpc 2015-11-19 10:21:23 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/RHEA-2015-2301.html