Am Sonntag, 29. März 2015, 15:26:51 schrieben Sie:
> dear Martin,

Dear Jaromil,

> On Sun, 29 Mar 2015, Martin Steigerwald wrote:
> > Bug#761658: Please do not default to using Google nameservers
>
> tl;dr - isn't there a preseed directive to change the default?!

I have no idea, I think I have read it is *hardcoded* into systemd-
resolved, but I didn´t check, so take this with a grain of salt. It seems
you can only disable this behavior by configuring a DNS server.

>From resolved.conf(5):

       FallbackDNS=
           A space separated list of IPv4 and IPv6 addresses to be
           used as the fallback DNS servers. Any per-interface DNS
           servers obtained from systemd-networkd.service(8) take
           precedence over this setting, as do any servers set via
           DNS= above or /etc/resolv.conf. This setting is hence only
           used if no other DNS server information is known. If this
           option is not given, a compiled-in list of DNS servers is
           used instead.

Okay, it depends whether it is possible to set this on a zero value.
If that doesn´t work it may work with setting it to 127.0.0.1 or even
a non existing 127.0.0.0/8 address.

I set it to an empty value now. But how do I get confirmation that it
works? Do I really have to deconfigure DNS to find out?

> > Marco tagged it as "wontfix". Seriously, if I didn´t configure a
> > nameserver I *mean* it. I don´t want it to just choose a Google
> > nameserver then, without even telling me.
>
> you are right in pointing this out. Also the /etc/resolv.conf situation
> is really sub-optimal as it is already in Wheezy, let me explain: I can
> understand the advantages of /etc/network/interfaces, but I would expect
> at least one of the manpages indicated in the generated file notice to
> detail how to deactivate this behavior and have /etc/resolv.conf
> generated by hand or another script.

I didn´t even report the bug, but I was surprised how Marco just closed it
as wontfix. But on the other hand I see a pattern there. I have seen that
with systemd related bug reports as well.

Its more this "I won´t fix this, go away" attitude I have seen with
systemd upstream and with Debian packagers of systemd than systemd itself
that lets me ponder to avoid systemd at least for my server VM.

Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7