UNIT                       LOAD   ACTIVE SUB    DESCRIPTION
● unbound-resolvconf.service loaded failed failed Unbound asyncronous resolvconf update helper

Logs:

Apr 27 18:05:19 my.example.org systemd[1]: Started unbound-resolvconf.service - Unbound asyncronous resolvconf update helper.
Apr 27 18:05:19 my.example.org resolvconf[870]: Dropped protocol specifier '.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1).
Apr 27 18:05:19 my.example.org resolvconf[870]: No DNS servers specified, refusing operation.
Apr 27 18:05:19 my.example.org systemd[1]: unbound-resolvconf.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 18:05:19 my.example.org systemd[1]: unbound-resolvconf.service: Failed with result 'exit-code'.

I found a related PR https://github.com/NLnetLabs/unbound-manual/pull/55, which is part of

https://unbound.docs.nlnetlabs.nl/en/latest/use-cases/local-stub.html#configuring-the-local-stub-resolver

I am not an expert at the area. But I believe cloudron does not need this service.

I disabled and mask it in one cloudron instance, until now everything seems to working and sudo systemctl --failed is clean again.

sudo systemctl mask unbound-resolvconf.service
sudo systemctl disable --now unbound-resolvconf.service

Is this service required for Cloudron, or is it safe to keep masked?