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 was initially created as a clone of Bug #622617 +++
Created attachment 437726[details]
DNS LDIF Example
Description of problem:
Latest version of bind-dyndb-ldap does not work with subdomains that are configured in ldap. Main domain (i.e. example.com) is loaded fine:
------------------------------------------------
querying 'idnsName=example.com,ou=Dynamic,ou=DNS,ou=Sluzby,dc=example,dc=com' with '(objectClass=idnsRecord)'
entry count: 1
------------------------------------------------
but all subdomains are loaded with errors:
------------------------------------------------
querying 'idnsName=srv, idnsName=example.com,ou=Dynamic,ou=DNS,ou=Sluzby,dc=example,dc=com' with '(objectClass=idnsRecord)'
entry count: 1
zone srv.example.com/IN: has 0 SOA records
zone srv.example.com/IN: not loaded due to errors.
------------------------------------------------
Complete example is in attachment. Subdomain (srv.example.com) is configured as record (idnsName=srv) in main domain (example.com) with NS records and also is placed in DNS container (like main domain) with SOA, NS records in object and classic zone records as subtree.
Version-Release number of selected component (if applicable):
bind-dyndb-ldap-0.1.0-0.9.a1.20091210git.fc13.x86_64
bind-9.7.1-2.P2.fc13.x86_64
openldap-2.4.21-9.fc13.x86_64
How reproducible:
always
Steps to Reproduce:
1. import attachment
2. configure ldap section in named.conf to correct LDAP subtree
3. restart named
4. try to query pdc.srv.example.com
Actual results:
return code of query is SERVFAIL
Expected results:
return code of query should be NOERROR
query of record ares.example.com will succeeded.
Additional info:
With version bind-dyndb-ldap-0.1.0-0.5.a1.fc13.x86_64 (recompliled from fc12) everything works fine:
zone srv.example.com/IN: sending notifies (serial 2009083001)
I do no if the DNS structure in LDAP was changed, bud I could not find any info about changes. I am using latest schema distributed with last version of bind-dyndb-ldap. Subtree example is not included with package and I have configured it like with file backend in named.
Verified.
testrelm already exists.
Added a subdomain and a a record:
[root@ipaqa64vmb ~]# ipa dnszone-add
Zone name: sub.testrelm
Authoritative nameserver: ipaqa64vmb.testrelm
Administrator e-mail address [root.sub.testrelm.]:
Zone name: sub.testrelm
Authoritative nameserver: ipaqa64vmb.testrelm.
Administrator e-mail address: root.sub.testrelm.
SOA serial: 2011270401
SOA refresh: 3600
SOA retry: 900
SOA expire: 1209600
SOA minimum: 3600
Active zone: TRUE
Dynamic update: FALSE
[root@ipaqa64vmb ~]# ipa dnsrecord-add sub.testrelm vma --a-rec=1.2.3.4
Record name: vma
A record: 1.2.3.4
Digging for the a record in the subdomain works.
[root@ipaqa64vmb ~]# dig vma.sub.testrelm
;; ANSWER SECTION:
vma.sub.testrelm. 86400 IN A 1.2.3.4
Bind is now running, despite the connection error.
Verified against:
ipa-server-2.0.0-23.el6.x86_64
bind-dyndb-ldap-0.2.0-3.20110426T0344z.el6.x86_64
bind-9.7.3-2.el6.x86_64
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0606.html