Bug 47836 – setup of AD Connection / AD Connector fails for AD DCs without DNS

Bug 47836 - setup of AD Connection / AD Connector fails for AD DCs without DNS


Summary:	setup of AD Connection / AD Connector fails for AD DCs without DNS

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.3
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-09-19 12:19 CEST by Ingo Steuwer
Modified:	2021-05-14 16:34 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
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.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
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 Ingo Steuwer

2018-09-19 12:19:02 CEST

Scenario:
- AD is used without DNS
- DNS is on separate, non-AD servers (including all needed service records)
- setup of AD Connection / AD Connector or join into AD Domain during installation of UCS fails

UMC shows an error message "Connection to AD Server <IP/FQDN> failed".

The setup process calls "lookup_adds_dc" from admember.py in univention-libs, which tries to use "dig" with the given AD DC as DNS server. In case this fails the AD Connector wizard stops.

We should make that configurable, or (better) an optional test which results in a question in UMC if the setup should be continued.

Comment 1 Ingo Steuwer

2018-09-19 12:20:20 CEST

Potential Workaround (untested):

Edit /usr/share/pyshared/univention/lib/admember.py line 710:

* orginal
def lookup_adds_dc(ad_server=None, ucr=None, check_dns=True):

* workaround
def lookup_adds_dc(ad_server=None, ucr=None, check_dns=False):

Comment 2 Ingo Steuwer

2018-09-21 13:27:54 CEST

(In reply to Ingo Steuwer from comment #1)
> Potential Workaround (untested):
> 
> Edit /usr/share/pyshared/univention/lib/admember.py line 710:
> 
> * orginal
> def lookup_adds_dc(ad_server=None, ucr=None, check_dns=True):
> 
> * workaround
> def lookup_adds_dc(ad_server=None, ucr=None, check_dns=False):

This change doesn't fix all issues in the scenario. Seems like the AD DC is also defined as Nameserver in /etc/resolv.conf

Comment 3 Ingo Steuwer

2021-05-14 15:13:16 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 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.