[Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

@diabloneo

resolvconf doesn't leave a process running on the system; it is only
triggered when there are changes to the network or to the available
local resolvers, and coordinates updates to /etc/resolv.conf.

But if /etc/resolv.conf is not a symlink to /run/resolvconf/resolv.conf,
this has no effect.

And if NetworkManager had written its own contents to /etc/resolv.conf,
that means either it was not a symlink to /run/resolvconf/resolv.conf,
or you were using a buggy version of NetworkManager.  (The Ubuntu
package of NetworkManager detects when resolvconf is in use, and avoids
overwriting /etc/resolv.conf.)

The question is how your system got into that state in 17.04.  But this
may not be a question we are able to answer after the fact.

If you have any further insight into how your system got into this
state, we would be interested to know.  Otherwise, I recommend you
follow Dimitri's guidance from comment #27 to return your system into a
supported configuration.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netcfg in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  ----

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  ----

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+subscriptions