Public bug reported:
Currently network-manager bin:pkg on Ubuntu 24.04 and up ships
/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which forces
NetworkManger to configure systemd-resolved as DNS resolver. However
network-manager does not Depends: on systemd-resolved bin:pkg, which can
lead to a situation where /etc/resolv.conf points to non-existent
systemd-resolved.
Since it's possible to use NetworkManager without systemd-resolved, we
should not enforce the use of systemd-resolved from network-manager
bin:pkg. Instead, I think it might be more appropriate to ship this file
from systemd-resolved bin:pkg instead. It might look strange, but I
think it's an OK thing to do. If NetworkManger is not installed, then
nothing happens. But if NetworkManger is installed, then NetworkManager
will start using systemd-resolved.
What do you think?
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097792
Title:
Don't ship 10-dns-resolved.conf within network-manager bin:pkg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2097792/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
