Bug 48416 – AD Member Mode: No DNS Reverse Zone entries in AD for UCS systems

Bug 48416 - AD Member Mode: No DNS Reverse Zone entries in AD for UCS systems


Summary:	AD Member Mode: No DNS Reverse Zone entries in AD for UCS systems

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:	2019-01-03 10:56 CET by Stephan Hendl
Modified:	2021-05-14 16:34 CEST (History)
CC List:	5 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?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016092921000325
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 2019-01-03 10:56:20 CET

+++ This bug was initially created as a clone of Bug #42537 +++

UCS 4.1-3 errata 282
Windows Server 2012 R2

I joined several UCS systems as part of an existing Active Directory domain (AD Member Mode). The UCS systems do have DNS entries in the Forward Zone of the Active Directory, but no Reverse Zone entries:

Windows AD DC: ada.future-inc.example.org - 10.200.30.177
UCS Master: mary.future-inc.example.org - 10.200.30.166

> nameserver1: 10.200.30.177
> nameserver2: <empty>
> nameserver3: <empty>

> root@mary:~# host mary
> mary.future-inc.example.org has address 10.200.30.166
> root@mary:~# host 10.200.30.166
> Host 166.30.200.10.in-addr.arpa. not found: 3(NXDOMAIN)

> root@mary:~# host 10.200.30.177
> 177.30.200.10.in-addr.arpa domain name pointer ada.future-inc.example.org.

Comment 1 Stephan Hendl 2019-01-03 10:56:59 CET

This issue should be investigated further since the problem is not solved yet.

Comment 2 Ingo Steuwer

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