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.

Bug 1168131

Summary:	Crash caused by NS record & forward zone interaction
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Kosek <mkosek>
Component:	bind-dyndb-ldap	Assignee:	Petr Spacek <pspacek>
Status:	CLOSED ERRATA	QA Contact:	Namita Soman <nsoman>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.0	CC:	nsoman, pspacek
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	bind-dyndb-ldap-6.0-2.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 09:29:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1114013

Description Martin Kosek 2014-11-26 08:41:38 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/145

= Problem =
Named crashed while deleting NS record from authoritative zone.

== Steps to Reproduce ==
{{{
ipa dnszone-add example.com
ipa dnsforwardzone-add fw.example.com --forwarder=192.0.2.1
ipa dnsrecord-add example.com fw --ns-rec=localhost.
ipa dnsrecord-del example.com fw
}}}

I was working with forward zones, and NS records which were same in FQDN form as forward zone. Maybe I will figure out what exactly causes the error.

{{{
Nov 21 09:25:18 ipa.example.com named-pkcs11[3605]: forward zone 'fw2.example.com': loaded
Nov 21 09:33:57 ipa.example.com named-pkcs11[3605]: forward zone 'fw3.example.com': loaded
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: ldap_helper.c:4365: INSIST(iszone == isc_boolean_true) failed, back trace
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: #0 0x7f4fe52e99a0 in ??
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: #1 0x7f4fe4855e9a in ??
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: #2 0x7f4fde2b4945 in ??
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: #3 0x7f4fe4875a86 in ??
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: #4 0x7f4fe2a68f33 in ??
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: #5 0x7f4fe1d0cded in ??
Nov 21 10:30:29 ipa.example.com named-pkcs11[3605]: exiting (due to assertion failure)
}}}


= Environment =
{{{
bind-libs-9.9.4-20.fc20.pkcs11.x86_64
bind-pkcs11-utils-9.9.4-20.fc20.pkcs11.x86_64
bind-utils-9.9.4-20.fc20.pkcs11.x86_64
bind-lite-devel-9.9.4-20.fc20.pkcs11.x86_64
bind-libs-lite-9.9.4-20.fc20.pkcs11.x86_64
bind-9.9.4-20.fc20.pkcs11.x86_64
bind-pkcs11-libs-9.9.4-20.fc20.pkcs11.x86_64
bind-license-9.9.4-20.fc20.pkcs11.noarch
bind-pkcs11-9.9.4-20.fc20.pkcs11.x86_64
bind-dyndb-ldap-6.0-6.fc20.x86_64
}}}
Just for note, I also had root zone in LDAP.

* Part of IPA installation
Yes
 
* Do you have some global forwarders configured in BIND configuration file? (Statements forward and forwarders.)
Yes

Comment 3 Petr Spacek 2014-11-27 15:45:47 UTC

Fixed upstream: https://fedorahosted.org/bind-dyndb-ldap/changeset/584f9ceeef131145feb32a741a8f5dbc04b9a2cd/

Comment 6 Namita Soman 2015-01-22 23:09:22 UTC

Verified using:
bind-dyndb-ldap-6.0-2.el7.x86_64
ipa-server-4.1.0-15.el7.x86_64



Followed steps from #comment1 

# ipa dnszone-add example.com
  Zone name: example.com.
  Active zone: TRUE
  Authoritative nameserver: qeblade6.testrelm.test.
  Administrator e-mail address: hostmaster
  SOA serial: 1421966678
  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 dnsforwardzone-add fw.example.com --forwarder=192.0.2.1
  Zone name: fw.example.com.
  Active zone: TRUE
  Zone forwarders: 192.0.2.1
  Forward policy: first


# ipa dnszone-find
  Zone name: 4.16.10.in-addr.arpa.
  Active zone: TRUE
  Authoritative nameserver: qeblade6.testrelm.test.
  Administrator e-mail address: hostmaster.testrelm.test.
  SOA serial: 1421958832
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  Allow query: any;
  Allow transfer: none;

  Zone name: example.com.
  Active zone: TRUE
  Authoritative nameserver: qeblade6.testrelm.test.
  Administrator e-mail address: hostmaster
  SOA serial: 1421966681
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  Allow query: any;
  Allow transfer: none;

  Zone name: testrelm.test.
  Active zone: TRUE
  Authoritative nameserver: qeblade6.testrelm.test.
  Administrator e-mail address: hostmaster.testrelm.test.
  SOA serial: 1421965755
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  Allow query: any;
  Allow transfer: none;
----------------------------
Number of entries returned 3
----------------------------



# ipa dnsrecord-add example.com fw --ns-rec=localhost.
  Record name: fw
  NS record: localhost.



# ipa dnsrecord-find example.com 
  Record name: @
  NS record: qeblade6.testrelm.test.

  Record name: _kerberos
  TXT record: TESTRELM.TEST

  Record name: fw
  NS record: localhost.
----------------------------
Number of entries returned 3
----------------------------


# ipa dnsrecord-del example.com fw
No option to delete specific record provided.
Delete all? Yes/No (default No): yes
-------------------
Deleted record "fw"
-------------------


# ipa dnsforwardzone-find example.com
  Zone name: fw.example.com.
  Active zone: TRUE
  Zone forwarders: 192.0.2.1
  Forward policy: first
----------------------------
Number of entries returned 1
----------------------------

Comment 7 Namita Soman 2015-01-22 23:12:02 UTC

/var/log/messages ended with 
Jan 22 17:48:16 qeblade6 named[32136]: forward zone 'fw.example.com': loaded

no crash msgs

Comment 9 errata-xmlrpc 2015-03-05 09:29:28 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