Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/99
Now we are mixing zone types 'master' and 'forward' in the single thing (in IPA UI and in objectClass 'idnsZone').
Zone types recognized in BIND: http://www.zytrax.com/books/dns/ch7/zone.html#type
Current situation leads to confusion for users because:
* Behaviour is not well defined (in BIND it is possible to set forwarders for 'master' zones with different effect than for 'forward' zones)
* BIND documentation is not applicable
* Users are forced to create imaginary SOA record (which is never seen by client) even for 'forward' zones
* It is possible to create subordinate records in 'forward' zone but these records are ignored
Proposal:
* Use existing objectClass 'idnsZone' for master zones (no change).
* Create a new objectClass 'idnsForwardZone'
mandatory single-value attribute idnsName (for RDN, same as in 'idnsZone')
mandatory multi-value attribute idnsForwarders (same as in 'idnsZone')
optional single-value attribute idnsForwardPolicy (same as in 'idnsZone')
I had a discussion with Petr, given that this bug was already part of the rebase in 7.0 (see Fixed In Version) and 7.0 GA'd last week, it makes little sense to keep it open. Closing the bug.