#123 LDAP MODRDN (rename) on records is not supported
Closed: Fixed None Opened 7 years ago by pspacek.

This is a limitation of initial implementation of wiki:BIND9/Design/RBTDB.

Named has to be restarted to resynchroniza data after each LDAP rename.


Fixing this bus will require a lot of additional code because we have to build LDAP UUID=>DNS name mapping.

Results of planning meeting held on 2014-11-04.

Steps to test

  • Add a record to a zone
  • Verify that it is visible in DNS
  • Rename the record
  • Use dig to verify that renamed record is not visible in DNS under old name and is visible under the new name

Implementation requires additional information from meta-database.

It was decided today that renaming zones is out of scope of this ticket.

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 22

4 years ago

Login to comment on this ticket.

Metadata