Bug#923082: can't disable systemd-resolved

Hi, Toni Mueller writes: > On Sun, Feb 24, 2019 at 08:03:38AM +0100, Martin Pitt wrote: >> resolved doesn't run in pid 1 (that would be a really bad architecture!). >> This >> just means that pid 1 connected to localhost's name server to resolve a name >> (i. e. a DNS client). A better command

Bug#923082: can't disable systemd-resolved

Hi Martin, On Sun, Feb 24, 2019 at 08:03:38AM +0100, Martin Pitt wrote: > Toni [2019-02-23 23:05 +]: > > I can't disable systemd-resolved, which prevents me from running my own > > DNS setup: > > systemd-resolved.service is not enabled by default in Debian. If you enabled > it, what

Bug#923082: can't disable systemd-resolved

Control: tag -1 moreinfo Hello Toni, Toni [2019-02-23 23:05 +]: > I can't disable systemd-resolved, which prevents me from running my own > DNS setup: systemd-resolved.service is not enabled by default in Debian. If you enabled it, what prevents you from disabling it again? (systemctl