Bug 48230 – Repository servers not reachable after AD-Takeover, dns/forwarder1 still points to IP of old AD-DC

Bug 48230 - Repository servers not reachable after AD-Takeover, dns/forwarder1 still points to IP of old AD-DC


Summary:	Repository servers not reachable after AD-Takeover, dns/forwarder1 still poin...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Takeover
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-11-28 16:30 CET by Arvid Requate
Modified:	2021-05-14 16:33 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
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 Arvid Requate

2018-11-28 16:30:50 CET

After an AD-Takeover I had the situation that the new UCS Samba/AD DC Master was unable to reach the external update servers.

Before the AD-Takeover the DNS resolution was possible because the AD-Server forwarded to an external DNS server. After the AD-Takeover the IP address of the old MS AD-Server has been assigned to a virtual network interface of the UCS system (eth0:1 in my case). UCR still points this IP:

nameserver1=<IP of old MS AD-Server>
dns/forwarder1=<IP of old MS AD-Server>

We should adjust the dns/forwarder1 in this case. Either through some magic (like looking up the DNS resolver config of the MS AD via powershell or something during the takeover) or (probably better) by checking if repository/online/server is reachable and otherwise interactively asking the Administrator to supply the IP address of a suitable DNS forwarder.

Comment 1 Ingo Steuwer

2021-05-14 15:13:11 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.