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.
Cause: Some internal flags are checked during loading without proper locking. Results are not reliable and suffer from a race condition.
Consequence: Sending notifies after zone load is not always sent to all secondary servers as it should.
Fix: Check loading status always when data is locked, ensuring race condition does not exist in multiple worker threads.
Result: Zone loading is more reliable and notifies are always sent out.
Created attachment 1829777[details]
Patch modified to apply on top of bind-9.11.4-26.P2.el7_9.3
Description of problem:
When doing a mass update of authoritative zones, the notifies are not always sent to the slave servers causing a delay in synchronization of the DATA across the DNS infrastructure.
Version-Release number of selected component (if applicable):
bind-9.11.4-26.P2.el7_9.3.x86_64
How reproducible:
Hard, at customer site only
Steps to Reproduce:
1. Define ~20 authoritative zones on a multi-processor system (the more CPUs the better)
2. Make sure the zones have a slave defined using "IN NS" resource records.
3. Start named.
4. Increase serial in the SOA for all zones
5. # rndc reload
Actual results:
Reload and the change of serial is detected, but the "sending notifies" line is not always sent for all the changed zones.
This is not always logged for all zones:
"notify: info: zone example001.com/IN: sending notifies (serial 2)"
Expected results:
All slaves are sent a notify.
Additional info:
Fix/Patch: https://gitlab.isc.org/isc-projects/bind9/-/commit/56003e9f9f72c8be67d553f4dbd16eba849ca864?merge_request_iid=795
Customer verified a fix in a test package.
RHEL-8.4 not affected (contains the fix already)
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 (bind bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:4784