Bug 48316 - Reverse DNS entry of Master not available after installation of Samba AD DC
Reverse DNS entry of Master not available after installation of Samba AD DC
Status: CLOSED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Samba 4
UCS@school 4.3
Other other
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-12-12 19:38 CET by Michael Grandjean
Modified: 2023-06-08 13:39 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2018-12-12 19:38:28 CET
During a workshop today:

We installed:
1. UCS Master 4.3-3
2. UCS@school 4.3 v6
3. Samba AD DC on UCS Master

After the switch of the DNS backend for bind9, the PTR record for the IP address of the Master did not resolve to the hostname/FQDN. Instead, bind9 returned "NXDOMAIN". The A record was fine, though.

We recognized this only, because during the system setup of the first UCS@school Slave a pre-join DNS check tested if the IP address is resolvable. Unfortunately the error message is a bit misleading: "No UCS DC Master could be found at the address." That's true, but a hint that the PTR lookup went wrong would be great. I spent quite some time investigating the A record und SRV records (_domaincontroller_master._tcp) first.

In our case, we were not able to join the slave until the underlying issue was resolved.

In the end, a simple restart of bind9 on the Master resolved the issue.
Comment 1 Arvid Requate univentionstaff 2019-01-07 16:42:27 CET
We need logs here: connector-s4.log, setup.log, updater.log, join.log
Comment 2 Jan-Luca Kiok univentionstaff 2023-06-08 13:39:29 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and UCS components may have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.