Bug 40967 - S4-Connector rejects for DNS records of Apple Mac clients
S4-Connector rejects for DNS records of Apple Mac clients
Status: RESOLVED DUPLICATE of bug 41190
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-x
Assigned To: Connector maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-31 13:39 CEST by Arvid Requate
Modified: 2016-05-03 14:17 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Troubleshooting
Max CVSS v3 score:


Attachments
sync_to_ucs_deduplicate_DNS_TYPE_A.patch (806 bytes, patch)
2016-03-31 13:39 CEST, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2016-03-31 13:39:53 CEST
Created attachment 7570 [details]
sync_to_ucs_deduplicate_DNS_TYPE_A.patch

Ticket# 2016033021000182 reports S4-Connector rejects (sync_to_ucs) for DNS records of Apple Mac clients.

The corresponding objectClass=dnsNode object in the DNS forward zone shows a dnsRecord multivalue attribute that contains multiple occurrences of the same IP (v4) address. In the AD object data this is possible because the dnsRecord values are blobs which also contain the timestamp of the value, so the raw LDAP attribute values differ even though the IP address is the same. The S4-Connector sh/could detect these duplicate records and only write the set of de-duplicated values to OpenLDAP (patch proposal attached, addresses ipv6 as well).

Actually the Mac clients seem to behave messy here. Windows clients delete their previously registered RR records in DNS first when they update their DNS records.
Comment 1 Arvid Requate univentionstaff 2016-05-03 14:17:45 CEST
More info on this: This might be caused by dlz_bind9 not treating objects properly that are marked as dNSTombstoned: TRUE. Marking as duplicate.

*** This bug has been marked as a duplicate of bug 41190 ***