Re: [knot-resolver-users] Running knot-resolver with only kresd-tls.socket

`systemctl mask kresd.socket` is the correct approach. I tested this with a clean installation of Knot Resolver 3.2.1 and the service works as expected (it is in 'active' state, not 'degraded'). I'd suggest to remove any drop-ins to restore the service and sockets to its pristine state, do `systemctl daemon-reload` and try masking the kresd.socket again. If you're still able to reproduce the degraded state, please tell us which OS distribution you use and its systemd version to debug this further.