Cubic

  1. Bug #1725840
  2. Comment #10

Comment 10 for bug 1725840

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

On Sat, Nov 04, 2017 at 06:55:17AM -0000, Matteo Dell'Amico wrote:
> Same bug for me: /etc/resolv.conf was pointing to
> /run/NetworkManager/resolv.conf rather than
> ../run/resolvconf/resolv.conf, as fixed by dpkg-reconfigure resolvconf.

> Bug also confirmed by a bunch of other people: see
> https://askubuntu.com/questions/966870/dns-not-working-after-
> upgrade-17-04-to-17-10/967341 .

Unfortunately this is the sort of problem that is very difficult to debug
after the fact, particularly as the kinds of changes users make to try to
resolve the problem for themselves tend to erase necessary clues.

If someone has /etc/resolv.conf as a symlink to
/run/NetworkManager/resolv.conf, it would be helpful to know the timestamp
of that symlink, which we could then correlate with package upgrade logs.