Bug 45761 - S4-Connector doesn't properly handle add+delete of host record with same name as zone
S4-Connector doesn't properly handle add+delete of host record with same name...
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-22 16:03 CET by Arvid Requate
Modified: 2022-03-15 09:39 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.143
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017112221000537
Bug group (optional): bitesize
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-11-22 16:03:40 CET
Ticket #2017112221000537 reports a case, where the administrator accidentally added a DNS host record "zone1.com" below the DNS forward zone "zone1.com".

Then the admin deleted the record again.

As a result the S4-Conenctor removed the SOA-record DC=@ from Samba/AD and after the next bind9 restart the DNS server doesn't find the zone any longer and doesn't resolve any of the host records existing in that zone.

The S4-Connector should not confuse the DNS host record with the zone. I guess somewhere an LDAP search filter needs to be adjusted.
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:52:05 CEST
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.