On 7/16/20 9:37 AM, Santiago Ruano Rincón wrote:
> I leave this as a note: kresd upstream removed systemd sockets support
> since 5.0:
> https://gitlab.nic.cz/knot/knot-resolver/-/issues/485
I'm afraid I don't understand what this has to with the original problem.
the original problem is the following:
* user did 'apt install knot-resolver' on buster,
edited resolv.conf to point to 127.0.0.1
* user upgrades from buster to bullseye and has no working
DNS anymore. there is no warning or anything.
I suggest to, please:
* either fix the package so that 'apt install knot-resolver' in
bullseye is again resulting in a working DNS resolver on localhost
* or, add a prominent warning note via debconf so people know
that they have to fix it manually and document the required
steps to configure knot-resolver to be used as a local resolver.
unless either of which is done, knot-resolver from bullseye *breaks*
peoples systems without saying so and in an unexpected way, which
deserves severity serious.
Regards,
Daniel