Bug 1139776
Summary: | LDAP MODRDN (rename) is not supported | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Petr Spacek <pspacek> | ||||
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: | akasurde, mkosek, mnavrati, pspacek | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | bind-dyndb-ldap-7.99-1.GIT158e95e.el7 | Doc Type: | Known Issue | ||||
Doc Text: |
The latest version of the bind-dyndb-ldap system plug-in offers significant improvements over the previous versions, but has some currently certain limitations. One of the limitations is missing support for the LDAP rename (MODRDN) operation. As a consequence, DNS records renamed in LDAP are not served correctly. To work around this problem, restart the named daemon to resynchronize data after each LDAP rename (MODRDN) operation. In an Identity Management (IdM) cluster, restart the named daemon on all IdM replicas.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-11-19 10:20:52 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: | 1204110 | ||||||
Bug Blocks: | 1168850, 1179458 | ||||||
Attachments: |
|
Description
Petr Spacek
2014-09-09 15:29:54 UTC
Know Issue text was added. 2 comments to the Known Issue doc: 1) You should note that it needs to be restarted on *all IdM servers* with DNS service, not just the one where the change as done. 2) Isn't named reload enough (and more user friendly) than full named restart? (In reply to Martin Kosek from comment #2) > 1) You should note that it needs to be restarted on *all IdM servers* with DNS service, not just the one where the change as done. Good point! I have updated the text. > 2) Isn't named reload enough (and more user friendly) than full named > restart? From bind-dyndb-ldap's point of view it is the same. Fixed upstream: eb599ae5b3b7a3f86237f60830357bd53deab012, a1f960e1edd4c6317d81e48a9b57f9c87c581e22, ea561ba7e4af91eeef2f56834e32e3581d8e4123 This bug was fixed and the fix is documented as part of rebase bug 1204110. Created attachment 1080957 [details]
dns_ldap_a_rec_rename.log
Steps to verify : 1. Add a record to a zone 2. Verify that it is visible in DNS 3. Rename the record 4. Use dig to verify that renamed record is not visible in DNS under old name and is visible under the new name without requiring DNS restart Verifed. Package Version used:: bind-dyndb-ldap-8.0-1.el7.x86_64 ipa-server-4.2.0-12.el7.x86_64 ipa-server-dns-4.2.0-12.el7.x86_64 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/RHEA-2015-2301.html |