Bug 37094 - Allow deactivation of automatic SRV-Record refresh (dnsupdate)
Allow deactivation of automatic SRV-Record refresh (dnsupdate)
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-27 18:25 CET by Arvid Requate
Modified: 2020-07-03 20:54 CEST (History)
6 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
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.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016040721000411, 2017120821000151
Bug group (optional):
Max CVSS v3 score:
best: Patch_Available+


Attachments
ucr_dnsupdate.patch (613 bytes, patch)
2014-11-27 18:25 CET, 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 2014-11-27 18:25:21 CET
Created attachment 6481 [details]
ucr_dnsupdate.patch

The samba "dnsupdate" service periodically checks if a list of essential DNS records are present and refreshes them otherwise.

In one customer environment the UCS DC had several network interfaces, let's say one connected the client network and another to a backbone, and the backbone interface adresses should not be advertised to the clients.

The attached patch simply introduces a UCR variable which allows deactivation of the dnsupdate service. This would allow customers to manually adjust the DNS records.
Comment 1 Jens Thorp-Hansen univentionstaff 2016-04-07 16:35:20 CEST
requested again: Ticket#2016040721000411
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:54:31 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.