Univention Bugzilla – Bug 33633
dns object synchronization broken if dns object is deleted in samba4
Last modified: 2020-07-03 20:53:34 CEST
UCS 3.2 Master with S4 and a join Windows Client (Win7). The windows client was joined into the domain and a dns object was created. # win7pro, perf.test, dns, perf.test dn: relativeDomainName=win7pro,zoneName=perf.test,cn=dns,dc=perf,dc=test aRecord: 10.200.7.60 objectClass: top objectClass: dNSZone objectClass: univentionObject univentionObjectType: dns/host_record dNSTTL: 10800 relativeDomainName: win7pro zoneName: perf.test Now i deleted the dns object in the samba4 backend with -> ldbdel -H /var/lib/samba/private/sam.ldb "DC=WIN7PRO,DC=perf.test,CN=MicrosoftDNS,CN=System,DC=perf,DC=test" and the connector said "dns con2ucs: Ignore unkown dns object..." 03.12.2013 11:58:42,787 LDAP (INFO ): Search S4 with filter: (uSNChanged>=3899) 03.12.2013 11:58:42,804 LDAP (INFO ): encode_s4_object: attrib objectGUID ignored during encoding 03.12.2013 11:58:42,805 LDAP (INFO ): __dn_from_deleted_object: get DN from lastKnownParent (DC=perf.test,CN=MicrosoftDNS,CN=System,DC=perf,DC=test) and rdn (DC=WIN7PRO) 03.12.2013 11:58:42,805 LDAP (INFO ): object_from_element: DN of removed object: DC=WIN7PRO,DC=perf.test,CN=MicrosoftDNS,CN=System,DC=perf,DC=test 03.12.2013 11:58:42,806 LDAP (INFO ): _ignore_object: Do not ignore DC=WIN7PRO,DC=perf.test,CN=MicrosoftDNS,CN=System,DC=perf,DC=test 03.12.2013 11:58:42,807 LDAP (INFO ): _object_mapping: map with key dns and type con 03.12.2013 11:58:42,807 LDAP (INFO ): _dn_type con 03.12.2013 11:58:42,808 LDAP (INFO ): _ignore_object: Do not ignore DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test 03.12.2013 11:58:42,809 LDAP (INFO ): get_ucs_object: object not found: DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test 03.12.2013 11:58:42,809 LDAP (PROCESS): sync to ucs: [ dns] [ delete] DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test 03.12.2013 11:58:42,809 LDAP (INFO ): sync_to_ucs: set position to dc=perf.test,cn=dns,dc=perf,dc=test 03.12.2013 11:58:42,810 LDAP (INFO ): dns con2ucs: Object (DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test): {'dn': u'DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test', 'attributes': {'distinguishedName': [u'DC=WIN7PRO\\0ADEL:ca04afe3-5b08-4138-8d49-bbe196378e1c,CN=Deleted Objects,DC=perf,DC=test'], 'name': [u'WIN7PRO\nDEL:ca04afe3-5b08-4138-8d49-bbe196378e1c'], 'objectClass': [u'top', u'dnsNode'], 'isRecycled': [u'TRUE'], 'objectGUID': [u'\xe3\xaf\x04\xca\x08[8A\x8dI\xbb\xe1\x967\x8e\x1c'], 'dc': [u'WIN7PRO\nDEL:ca04afe3-5b08-4138-8d49-bbe196378e1c'], 'whenChanged': [u'20131203105839.0Z'], 'lastKnownParent': [u'DC=perf.test,CN=MicrosoftDNS,CN=System,DC=perf,DC=test'], 'whenCreated': [u'20131203100423.0Z'], 'uSNCreated': [u'3871'], 'uSNChanged': [u'3899'], 'instanceType': [u'4'], 'isDeleted': [u'TRUE']}, 'deleted_dn': u'DC=WIN7PRO\\0ADEL:ca04afe3-5b08-4138-8d49-bbe196378e1c,CN=Deleted Objects,DC=perf,DC=test', 'modtype': 'delete'} 03.12.2013 11:58:42,810 LDAP (INFO ): dns con2ucs: Ignore unkown dns object: DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test 03.12.2013 11:58:42,810 LDAP (INFO ): Return result for DN (DC=WIN7PRO,dc=perf.test,cn=dns,dc=perf,dc=test) 03.12.2013 11:58:42,816 LDAP (INFO ): _set_lastUSN: new lastUSN is: 3899 but the UCS LDAP object is still present -> univention-ldapsearch relativeDomainName=WIN7PRO -LLLL dn: relativeDomainName=win7pro,zoneName=perf.test,cn=dns,dc=perf,dc=test aRecord: 10.200.7.60 objectClass: top objectClass: dNSZone objectClass: univentionObject univentionObjectType: dns/host_record dNSTTL: 10800 relativeDomainName: win7pro zoneName: perf.test So, it seems that the synchronization of the dns objects is broken if the object is deleted in samba4
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.