resolvconf fails to update DNS server after resuming laptop from suspend

Bug #1787374 reported by pureblood
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This bug has been present since I have updated to Ubuntu 17.10 and it is still present in Ubuntu 18.04. It seems pretty simple to understand and a solution should be straightforward, but I lack understanding for what application is failing to update the right configuration file.

When I go to work and I start my laptop, my /run/resolvconf/interface/systemd-resolved is filled with this:
nameserver 127.0.0.53
search broadinstitute.org plc.hootoo.com

When I come back home, DNS resolution does not work or works very slowly, most likely because my work DNS server broadinstitute.org is not reachable anymore, or maybe it is reachable but it is excruciatingly slow at responding.

The solution is for me to edit /run/resolvconf/interface/systemd-resolved and remove the work DNS server:
nameserver 127.0.0.53
search plc.hootoo.com

And then update /etc/resolv.conf with the following command:
$ sudo /etc/init.d/resolvconf restart

Alternatively, another solution is to reboot the laptop. Then everything works fine. This is clearly a bug, but I am not sure whether it is a NetworkManager's bug, a resolvconf's bug, or a systemd bug. Please help! :-)

pureblood (freeseek)
affects: systemd (Ubuntu) → resolvconf (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in resolvconf (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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