For /etc/resolv.conf integration, a lot of more commonly local resolvers and integrators exist already, including DHCP clients etc, which do already conflict by times. So even if it is wanted with Unbound, it may cause less issues when leaving this to the admin, who knows whether/which other local resolver is used, and whether integration is wanted or not.
So in my opinion, most users is served best when leaving host DNS integration as opt-in. Hence I also vote for having `unbound-resolvconf.service` disabled by default, but against the `systemd-resolved` integration being active by default.
But I am all in for having by default inactive services, configs, or commented settings for common use cases, to make opting in any of them easy.
-- Best regards, Micha
OpenPGP_0x0442B9ADE65643FE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
