On Mon, 25 Feb 2019 14:29:42 +0000 Toni Mueller <t...@debian.org> wrote: > > > reopen 923081 > thanks > > > Hi Andreas, > > On Mon, Feb 25, 2019 at 09:25:48AM +0100, Andreas Henriksson wrote: > > (Not sure why you think Cloudflare is a problem but Google is not, but > > oh well.....) > > well, I think you are misreading my bug report. > > I definitely think that *both* are a problem, but until I took a closer > look, I was just unaware of this entire thing. And, btw, I would prefer > to use something that has sane defaults and can be used without > attending a special "systemd university" first - I just have different > priorities than that. > > > If *you* enable systemd-resolved (which is shipped completely disabled) > > then *you* are expected to know how to configure it. > > I don't know how you can conclude that *I* enabled it. In fact, it is > enabled by default as far as I can see, because there is only one way to > disable it, which is setting "DNSStubListener" to "no", while the > default is "yes", as also indicated by this snippet from the config file > as shipped in this file: systemd_240-6_amd64.deb: > > #DNSStubListener=yes > > Please see also the appropriate section about this option on this web > page: > > https://www.freedesktop.org/software/systemd/man/resolved.conf.html > > > Please don't claim that this service is disabled as shipped in Debian > when it is not.
Andreas is correct. systemd-resolved is *not* enabled by default in Debian. $ systemctl is-enabled systemd-resolved disabled If that reports a different state for you, then you have enabled the service manually. -- 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
