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/freeipa/ticket/3347

In order to properly manage DNS SOA serials we filter replication of this attribute, however the attribute needs to be created on the target replica as it is a required attribute for a Zone.

We should manage this in a ds plugin that monitors replication of new zones.
At the same time we could manage auto-serial-increment in this plugin as well so that we do not have to rely on bind-dynd-ldap to keep the attribute updated at all times.

This is important because not all IPA servers are DNS-enabled so bind-dyndb-ldap is not always around to 'fix' it for us.
A plugin would avoid any delay in getting the attribute 'fixed' as soon as a new zone is replicated.

Please add steps to verify this

This bug was marked as RFE by mistake. There is no functional change from previous versions.

Basic functionality is the same as described in:
https://bugzilla.redhat.com/show_bug.cgi?id=840383#c5

Your testing (probably) should concenrate to problems described in:
https://bugzilla.redhat.com/show_bug.cgi?id=895083

You should not see any problem even if option 'serial_autoincrement' is set to 'no' in /etc/named.conf. idnsSOAserial attribute should exist in all cases, including replicated DNS zones etc.

Verified in QE test for Bug 895083. Cross linking noted in TCMS. 

Verified against ipa-server-3.3.3-6.el7.x86_64

Based on Comment 2, this is not RFE and we thus do not plan to document it in 7.0.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.