Univention Bugzilla – Bug 39637
DNS: reverse zone not deleted in UDM/LDAP if deleted in Windows/Samba
Last modified: 2019-01-03 07:23:09 CET
UCS master s4 + joined windows 7 client Delete a reverse zone with the windows DNS-Manager. The Zone has been deleted in Samba4 but not in UDM/ldap.
Just came across this behavior troubleshooting a S4 dnsRecord issue. https://help.univention.com/t/ghost-dns-ptr-in-rsat-that-show-up-in-ucs-udm-no-rejects-suspect-dnsrecord-rank-flags-wrong/9060 Is current course of action to manually delete reverse zone in UDM? Regards.
Created attachment 9573 [details] bug39637_partial.diff Answering Comment 1: yes. The attached patch is just a start to fix this. The main todo I currently see is that univention.s4connector.s4.__dn_from_deleted_object probably should be adjusted for this, because lastKnownParent is also a deleted DN in this case: ======================================================================== dn: DC=@\0ADEL:666f62cc-15ae-433a-a7d1-fddd476a4cc3,CN=Deleted Objects,DC=DomainDnsZones,DC=ar41i1,DC=qa objectClass: dnsNode objectGUID: 666f62cc-15ae-433a-a7d1-fddd476a4cc3 isDeleted: TRUE lastKnownParent: DC=5.2.1.in-addr.arpa\0ADEL:134f44a5-c891-4255-803b-3f7b380dd3ac,CN=Deleted Objects,DC=DomainDnsZones,DC=ar41i1,DC=qa isRecycled: TRUE dc: @ DEL:666f62cc-15ae-433a-a7d1-fddd476a4cc3 ========================================================================
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.