This bug is created as a clone of upstream ticket:
This is a limitation of initial implementation of wiki:BIND9/Design/RBTDB.
Named has to be restarted to resynchroniza data after each LDAP rename.
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
From bind-dyndb-ldap's point of view it is the same.
eb599ae5b3b7a3f86237f60830357bd53deab012, a1f960e1edd4c6317d81e48a9b57f9c87c581e22, ea561ba7e4af91eeef2f56834e32e3581d8e4123
This bug was fixed and the fix is documented as part of rebase bug 1204110.
Created attachment 1080957 [details]
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
Package Version used::
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.