[Bug 1787374] Re: resolvconf fails to update DNS server after resuming laptop from suspend
Launchpad Bug Tracker
1787374 at bugs.launchpad.net
Fri Mar 15 12:42:41 UTC 2019
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1787374
Title:
resolvconf fails to update DNS server after resuming laptop from
suspend
Status in resolvconf package in Ubuntu:
Confirmed
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! :-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1787374/+subscriptions
More information about the foundations-bugs
mailing list