Public bug reported:
Since the last Network Manager upload my systems get a completely empty
/etc/resolv.conf when they'd before have a directly managed file by
NetworkManager.
I have dns=default set in NetworkManager.conf which tells NetworkManager
to directly manage that file. But that's now apparently ignored.
I managed to workaround the issue by turning /etc/resolv.conf into a static
file (as opposed to a symlink to the resolvconf path) but that shouldn't be
necessary at all.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647066
Title:
Systems with systemd-resolved disabled and dns=default in
NetworkManager.conf no longer get DNS
Status in network-manager package in Ubuntu:
New
Bug description:
Since the last Network Manager upload my systems get a completely
empty /etc/resolv.conf when they'd before have a directly managed file
by NetworkManager.
I have dns=default set in NetworkManager.conf which tells
NetworkManager to directly manage that file. But that's now apparently
ignored.
I managed to workaround the issue by turning /etc/resolv.conf into a static
file (as opposed to a symlink to the resolvconf path) but that shouldn't be
necessary at all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647066/+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
