Sorry for the delay here; I guess the bugtracker doesn't automatically subscribe the reporter.
What's the reason to install unbound when systemd-resolved is installed? Maybe it would be better to add Conflicts: systemd-resolved to unbound instead of allowing them to co-exists?
This bug was reported by a customer; I don't have a good answer to
this question right now. I've requested some additional context
regarding their use case.
Where that recommendation is, anyway?
See the bottom of the section linked at [1].
From all I'm seeing, the best solution seems to be to avoid installing
the two together. Or by adding "Conflicts: systemd-resolved.service"
or something like that to unbound-resolvconf.service, so it wont start
if resolved is running
Conflicts is a good idea; without more context from the customer, I
would consider that a suitable fix for this.
Thanks!
~Wesley
[1]
https://unbound.docs.nlnetlabs.nl/en/latest/use-cases/local-stub.html#ubuntu
[2]
https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#Conflicts=
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)