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 1161635 - DNS notify messages are not sent for modifications outside zone apex
Summary: DNS notify messages are not sent for modifications outside zone apex
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Petr Spacek
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks: 1168850
TreeView+ depends on / blocked
 
Reported: 2014-11-07 14:28 UTC by Petr Spacek
Modified: 2015-03-05 09:29 UTC (History)
2 users (show)

Fixed In Version: bind-dyndb-ldap-6.0-2.el7
Doc Type: Known Issue
Doc Text:
Need to be updated for inclusion in Beta release notes.
Clone Of:
Environment:
Last Closed: 2015-03-05 09:29:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0424 0 normal SHIPPED_LIVE bind-dyndb-ldap bug fix and enhancement update 2015-03-05 14:26:27 UTC

Description Petr Spacek 2014-11-07 14:28:43 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/144

This is a regression from RHEL 7.0.

DNS notify messages are not sent if modifications are made to zone names '''inside''' a zone.

By inside I mean e.g. name `test.idm.lab.eng.brq.redhat.com.` which part of zone `idm.lab.eng.brq.redhat.com`.

BIND should send `DNS notify` message when any object inside a zone is modified. This doesn't work in bind-dyndb-ldap 6.0+.

`Notify` messages are generated only if zone apex (`idm.lab.eng.brq.redhat.com.` in the example above) is modified.

Log message produced by BIND should look like this:
{{{
zone idm.lab.eng.brq.redhat.com/IN: sending notifies (serial 1415369834)
}}}
Comment 5 Petr Spacek 2014-11-27 16:27:42 UTC 
Fixed upstream: https://fedorahosted.org/bind-dyndb-ldap/changeset/7dd6ba6c70273fef0ffd34b265e6f1a1b6988a26/
Comment 10 Namita Soman 2015-01-23 14:16:19 UTC 
Verified using -
ipa-server-4.1.0-15.el7.x86_64
bind-dyndb-ldap-6.0-2.el7.x86_64

Steps taken:


# ipa dnszone-add example.test.
  Zone name: example.test.
  Active zone: TRUE
  Authoritative nameserver: vm-idm-001.testrelm.test.
  Administrator e-mail address: hostmaster
  SOA serial: 1422022040
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  BIND update policy: grant TESTRELM.TEST krb5-self * A; grant TESTRELM.TEST krb5-self * AAAA; grant TESTRELM.TEST krb5-self * SSHFP;
  Dynamic update: FALSE
  Allow query: any;
  Allow transfer: none;


# ipa dnsrecord-add example.test. @ --ns-rec='localhost.'
  Record name: @
  NS record: localhost., vm-idm-001.testrelm.test.


# date
Fri Jan 23 19:38:25 IST 2015


# ipa dnsrecord-add example.test. @ --txt-rec="Test notify after modification inside zone apex"
  Record name: @
  NS record: localhost., vm-idm-001.testrelm.test.
  TXT record: Test notify after modification inside zone apex


# date
Fri Jan 23 19:38:54 IST 2015


# ipa dnsrecord-add example.test. record-inside  --txt-rec="Test notify after modification outside zone apex"
  Record name: record-inside
  TXT record: Test notify after modification outside zone apex


# date
Fri Jan 23 19:39:17 IST 2015


# tail /var/log/messages 
Jan 23 19:37:33 vm-idm-001 nm-dispatcher: Dispatching action 'dhcp4-change' for eth0
Jan 23 19:37:56 vm-idm-001 named[21658]: zone example.test/IN: sending notifies (serial 1422022076)
Jan 23 19:37:56 vm-idm-001 named[21658]: client 127.0.0.1#20140: received notify for zone 'example.test'
Jan 23 19:37:56 vm-idm-001 named[21658]: client ::1#25943: received notify for zone 'example.test'
Jan 23 19:38:47 vm-idm-001 named[21658]: zone example.test/IN: sending notifies (serial 1422022127)
Jan 23 19:38:47 vm-idm-001 named[21658]: client 127.0.0.1#2710: received notify for zone 'example.test'
Jan 23 19:38:47 vm-idm-001 named[21658]: client ::1#9037: received notify for zone 'example.test'
Jan 23 19:39:15 vm-idm-001 named[21658]: zone example.test/IN: sending notifies (serial 1422022155)
Jan 23 19:39:15 vm-idm-001 named[21658]: client 127.0.0.1#11342: received notify for zone 'example.test'
Jan 23 19:39:16 vm-idm-001 named[21658]: client ::1#50426: received notify for zone 'example.test'


verified notify messages are generated for modifications outside zone apex
Comment 13 errata-xmlrpc 2015-03-05 09:29:26 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/RHBA-2015-0424.html
Note You need to log in before you can comment on or make changes to this bug.