Your message dated Sat, 06 Jun 2015 21:42:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#787731: adds google nameserver without being asked to
has caused the Debian Bug report #787731,
regarding adds google nameserver without being asked to
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
787731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787731
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17
Severity: normal
On all systems I checked, there is a file /etc/systemd/resolved.conf
with the following contents:
[19/516]mh@barrida:~$ cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# See resolved.conf(5) for details
[Resolve]
#DNS=8.8.8.8 8.8.4.4 2001:4860:4860::8888 2001:4860:4860::8844
[20/517]mh@barrida:~$
If I enable systemd-resolved, this ends up in the following resolv.conf:
[16/513]mh@barrida:~$ cat /run/systemd/resolve/resolv.conf
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.
nameserver 192.168.181.12
nameserver 8.8.8.8
nameserver 8.8.4.4
# Too many DNS servers configured, the following entries may be ignored
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
[17/514]mh@barrida:~$
Changing the commented out line in resolved.conf does not change
anything, so this must be the "compiled-in default".
The "nameserver 192.168.181.12" line that is generated on the system
in question originates in /etc/systemd/network/int181.network and is
the value that I -want- used.
The documentation in resolved.conf(5) suggests that the compiled-in
list does only apply if there is no other definition of DNS-Servers.
This is not the case here, and the fact that systemd-resolved takes
the definition from /etc/systemd/network/int181.network shows that it
knows that there is another definition.
Having google's resolvers in the first place poses a potential data
leak.
Greetings
Marc
--- End Message ---
--- Begin Message ---
Version: 217-1
Am 05.06.2015 um 22:53 schrieb Michael Biebl:
> I tested with a minimal configuration under jessie's v215 and could
> reproduce the problem.
> Upgrading to v220 solved the issue. Thus marking accordingly.
Specifically, this was fixed by
commit 4e945a6f7971fd7d1f6b2c62ee3afdaff3c95ce4
Author: Lennart Poettering <[email protected]>
Date: Fri Aug 1 16:04:12 2014 +0200
resolved: beef up DNS server configuration logic
We now maintain two lists of DNS servers: system servers and fallback
servers.
system servers are used in combination with any per-link servers.
fallback servers are only used if there are no system servers or
per-link servers configured.
This change is imho too invasive for being backported to the stable v215
in jessie. The first Debian version carrying that fix is 217-1, so I'm
closing it for this version.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
