Bug 90216

Summary:	resolved: 219 adds extra dns servers even when FallbackDNS is non empty
Product:	systemd	Reporter:	Henri Derycke <nheir.kim>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Henri Derycke 2015-04-28 13:31:21 UTC

When FallbackDNS is not empty in resolved.conf, resolved still adds defaults fallback dns (8.8.8.8…) to resolv.conf.

For example :

// resolved.conf
[Resolve]
FallbackDNS=80.67.169.12 2001:910:800::12
-----
// resolv.conf
nameserver 2001:4860:4860::8888
nameserver 8.8.4.4
nameserver 2001:910:800::12
# Too many DNS servers configured, the following entries may be ignored.
nameserver 80.67.169.12
nameserver 8.8.8.8
nameserver 2001:4860:4860::8844
-----

Since the man say “FallbackDNS= […] If this option is not given, a compiled-in list of DNS servers is used instead.” I assume that if FallbackDNS is not empty, the compile-in list is not used.

Comment 1 Lennart Poettering 2017-10-27 18:05:07 UTC

This has been fixed a while back, and should work correctly in v235. Please update.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.