RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1207541 - [RFE] Generic support for unknown DNS RR types (RFC 3597)
Summary: [RFE] Generic support for unknown DNS RR types (RFC 3597)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Picka
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks: 1181710 1211608
TreeView+ depends on / blocked
 
Reported: 2015-03-31 07:02 UTC by Martin Kosek
Modified: 2015-11-19 10:21 UTC (History)
2 users (show)

Fixed In Version: bind-dyndb-ldap-7.99-1.GIT158e95e.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 10:21:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Evidence of verify (1.77 KB, text/plain)
2015-09-22 12:15 UTC, Pavel Picka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:2301 0 normal SHIPPED_LIVE bind-dyndb-ldap bug fix and enhancement update 2015-11-19 09:55:21 UTC

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


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