Hi, On Wed, 28 Jun 2023, at 12:35, Alain Knaff wrote: > The current resolvconf leaves a confusing header message in > /etc/resolv.conf: > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > # 127.0.0.53 is the systemd-resolved stub resolver. > # run "resolvectl status" to see details about the actual nameservers. > > trying to run resolvectl suggests to apt install systemd-resolved > > Actually doing so, however, removes resolvconf, and breaks > /etc/resolv.conf more than it already was. It looks as if > systemd-resolved is a different (incompatible) approach from resolvconf, > and installing it actually removes resolvconf. > > The message should be fixed to avoid confusing people. Ok if people > actually want systemd to handle DNS, but they should not be sent there > if they currently have chosen a different approach.
When this message was written, it was possible to install resolved and resolvconf at the same time. Meanwhile though, resolved started shipping /sbin/resolvconf thus preventing resolvconf from being used with resolved. I voiced my opposition, but it wasn’t acted upon: https://bugs.debian.org/939904 I’m not sure what’s the best thing to do now. -- Cheers, Andrej
