Systems with systemd-resolved disabled and dns=default in NetworkManager.conf no longer get DNS
Bug #1647066 reported by
Stéphane Graber
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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 post a comment you must log in.
