Bug 39162 – S4-Connector duplicates dnsRecord values of S4 DNS Objects

Bug 39162 - S4-Connector duplicates dnsRecord values of S4 DNS Objects


Summary:	S4-Connector duplicates dnsRecord values of S4 DNS Objects

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-08-12 20:59 CEST by Arvid Requate
Modified:	2019-01-03 07:18 CET (History)
CC List:	1 user (show)

See Also:	42324
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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016033021000182
Bug group (optional):
Max CVSS v3 score:

Flags:	gohmann: Patch_Available+

Attachments
fix_srv_record_duplication.patch (3.23 KB, patch) 2015-08-12 20:59 CEST, Arvid Requate	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2015-08-12 20:59:16 CEST

Created attachment 7103 [details]
fix_srv_record_duplication.patch

In my tests for Bug 34184 I discovered that the S4-Connector duplicates the dnsRecord values on Samba4 DNS SRV record objects. The dnsRecord values are essentially identical, but they differ in at least three fields of the binary dnsRecord  structure: serialnumber, timestamp, ttl. To the S4-Connector the resulting binary blob values differ and so it adds both. I guess.

The attached patch doesn't quite fix this, but it was an attempt to understand a bit how this could happen.

Comment 1 Arvid Requate

2016-05-03 14:33:00 CEST

This also seems to happen for A/AAAA records (Ticket#: 2016033021000182):

===========================================================================
dnsRecord:     NDR: struct dnsp_DnssrvRpcRecord
        wDataLength              : 0x0010 (16)
        wType                    : DNS_TYPE_AAAA (28)
        version                  : 0x05 (5)
        rank                     : DNS_RANK_ZONE (240)
        flags                    : 0x0000 (0)
        dwSerial                 : 0x00000d9b (3483)
        dwTtlSeconds             : 0x00000384 (900)
        dwReserved               : 0x00000000 (0)
        dwTimeStamp              : 0x00000000 (0)
        data                     : union dnsRecordData(case 28)
        ipv6                     : 2a02:0908:e840:8e60:4ad7:05ff:feb2:e24f

dnsRecord:     NDR: struct dnsp_DnssrvRpcRecord
        wDataLength              : 0x0010 (16)
        wType                    : DNS_TYPE_AAAA (28)
        version                  : 0x05 (5)
        rank                     : DNS_RANK_ZONE (240)
        flags                    : 0x0000 (0)
        dwSerial                 : 0x00000d9b (3483)
        dwTtlSeconds             : 0x000004b0 (1200)
        dwReserved               : 0x00000000 (0)
        dwTimeStamp              : 0x00376ec7 (3632839)
        data                     : union dnsRecordData(case 28)
        ipv6                     : 2a02:0908:e840:8e60:4ad7:05ff:feb2:e24f

dnsRecord:     NDR: struct dnsp_DnssrvRpcRecord
        wDataLength              : 0x0010 (16)
        wType                    : DNS_TYPE_AAAA (28)
        version                  : 0x05 (5)
        rank                     : DNS_RANK_ZONE (240)
        flags                    : 0x0000 (0)
        dwSerial                 : 0x00000d9b (3483)
        dwTtlSeconds             : 0x000004b0 (1200)
        dwReserved               : 0x00000000 (0)
        dwTimeStamp              : 0x00377033 (3633203)
        data                     : union dnsRecordData(case 28)
        ipv6                     : 2a02:0908:e840:8e60:4ad7:05ff:feb2:e24f
===========================================================================

Comment 2 Stefan Gohmann

2019-01-03 07:18:13 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.