Bug 36679 – difference in root-server-usage between s4 and non-s4 setup

Bug 36679 - difference in root-server-usage between s4 and non-s4 setup


Summary:	difference in root-server-usage between s4 and non-s4 setup

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	DNS
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-14 09:31 CET by Philipp Hahn
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.011
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 Philipp Hahn

2014-11-14 09:31:18 CET

No forwarder was configured, so BIND uses its built-in ZONE for the DNS root servers to start resolving from there instead of delegating the resolve to a forwarder.

Without S4:
 dig apt.univention.de: NOTHING
 dig apt.univention.de -p 7777: A AAAA

With S4:
 dig apt.univention.de: A AAAA

Comment 1 Stefan Gohmann

2014-11-15 16:27:50 CET

AD has the root DNS servers in the DNS configuration by default:

univention-s4search -b DC=@,DC=RootDNSServers,CN=MicrosoftDNS,CN=System,$(ucr get connector/s4/ldap/base) | s4search-decode

Comment 2 Philipp Hahn

2015-11-11 16:44:14 CET

ucr unset dns/forwarder1
ucr set dns/fakeroot=no

With UCS-4.1 it seems to work after I've disabled IPv6 by doing `ucr set dns/debug/level='0 -4'`:
> error (network unreachable) resolving 'ns-1and1.ui-dns.de/A/IN': 2001:668:1f:11::105#53
> error (network unreachable) resolving 'ns-1and1.ui-dns.de/AAAA/IN': 2001:668:1f:11::105#53
> error (network unreachable) resolving 'ns-1and1.ui-dns.com/A/IN': 2001:8d8:fe:53:0:d9a0:52c2:100#53

Comment 3 Ingo Steuwer

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