Ubuntu
network-manager package

network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS

Bug #1803236 reported by Yoan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

During the do-release-upgrade from 16.04 to 18.04, if the user chooses to preserve the old NetworkManager.conf having "dns=dnsmasq", it does not preserve dnsmasq as the local resolver.

It results in a broken DNS configuration, with /etc/resolv.conf set to 127.0.0.53 but NetworkManager set to dnsmasq.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in network-manager (Ubuntu):
importance: Undecided → Low
Revision history for this message
Yoan (myoan) wrote :

Here it is:
https://bugzilla.gnome.org/show_bug.cgi?id=797383

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Please follow the instructions of Thomas Haller in your upstream bug report.

Changed in network-manager (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.