Bug 39161

Summary:	S4-Connector doesn't remove DDNS-deleted objects in UDM
Product:	UCS	Reporter:	Arvid Requate <requate>
Component:	S4 Connector	Assignee:	Samba maintainers <samba-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	gohmann
Version:	UCS 4.0	Flags:	gohmann: Patch_Available+
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=38713
What kind of report is it?:	Bug Report	What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains	How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069	Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:
Attachments:	fix_dns_object_removal.patch

Description Arvid Requate

2015-08-12 20:51:15 CEST

Created attachment 7102 [details]
fix_dns_object_removal.patch

When a DNS record is removed via DDNS (e.g. nsupdate), they don't get removed in UDM/OpenLDAP.

There are two issues that block this: The main one is, that Samba4/AD doesn't actually delete the objects in this case, but changes their type (wType) to DNS_TYPE_TOMBSTONE (See also Bug 38713).

Additionally, even if the object would be detected as removed, then some small code issues would cause a traceback. See the attached patch.

To fix the DNS_TYPE_TOMBSTONE I had to make use of the s4cache, to be able to identify the type of DNS object. The patch could be simplified by passing guid and old_s4_object from sync_to_ucs to the ucs_sync_function.

Comment 1 Stefan Gohmann

2019-01-03 07:17:28 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 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.