Bug 46855 – UMC ucs-sso module uses wrong name server

Bug 46855 - UMC ucs-sso module uses wrong name server


Summary:	UMC ucs-sso module uses wrong name server

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.2
Hardware:	Other Windows 7

Importance:	P5 normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-04-19 16:52 CEST by Stephan Hendl
Modified:	2020-07-03 20:55 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034
Enterprise Customer affected?:	Yes
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 Stephan Hendl 2018-04-19 16:52:48 CEST

We are using AD member mode and have configured two DNS servers via UCR.

ucr search nameserver
nameserver1: 192.168.1.254
nameserver2: 192.168.1.253

Querying these servers with dig gives the right answer:

dig ucs-sso.domain.local
;; ANSWER SECTION:
ucs-sso.domain.local. 900    IN      A       192.168.1.2
ucs-sso.domain.local. 900    IN      A       192.168.1.1

Even with AD member mode there are bind9-services running on DC-master, DC-backup as well as DC-slave servers. Querying the bind9-service on the DC-master the answer was wrong because there is an additional server...

nslookup ucs-sso 192.168.1.1
Server:         192.168.1.1
Address:        192.168.1.1#53

Name:   ucs-sso.domain.local
Address: 192.168.1.1
Name:   ucs-sso.domain.local
Address: 192.168.1.3
Name:   ucs-sso.domain.local
Address: 192.168.1.2

After deleting the wrong entry with .3 at the end via UDM web interface the sso-redirection worked again. So I guess the UMC module ignores the dns configuration made in /ertc/resolv.conf and uses bind9 or LDAP database directly.

Comment 1 Nico Stöckigt

2018-04-19 17:00:12 CEST

I would expect that in ad membermode the MS/AD DNS is used and the UCS DNS is ignored / not used.

Comment 2 Ingo Steuwer

2020-07-03 20:55:03 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.