Public bug reported:
In 24.04.1 it's possible to use systemd-resolved to manage DNS settings.
I have this set up on a server and am then running unbound as a caching
server for the local network.
The unbound install includes the unbound-resolvconf which now fails each
time due to the fact that systemd-resolved is managing the
/etc/resolv.conf file.
In debian there's a unbound defaults file that allows you to switch this
behaviour off using an environmental variable, but with ubuntu it
doesn't appear that this configuration is supported.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2085778
Title:
unbound-resolvconf.service in failed state using systemd-resolved
Status in systemd package in Ubuntu:
New
Bug description:
In 24.04.1 it's possible to use systemd-resolved to manage DNS
settings. I have this set up on a server and am then running unbound
as a caching server for the local network.
The unbound install includes the unbound-resolvconf which now fails
each time due to the fact that systemd-resolved is managing the
/etc/resolv.conf file.
In debian there's a unbound defaults file that allows you to switch
this behaviour off using an environmental variable, but with ubuntu it
doesn't appear that this configuration is supported.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2085778/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
