[Bug 1023486] Re: Cannot resolve domain names if eth0 is in /etc/network/interfaces

[Mathieu Trudel-Lapierre]

/etc/resolv.conf contains only 127.0.0.1, as introduced by NetworkManager.
/run/resolvconf/interface contains only NetworkManager, which has 127.0.0.1 with possibly a search and/or domain entry.
/etc/resolvconf/resolv.conf.d is irrelevant in this particular case and files wheren't changed. original however contains what it *probably* the information introduced by ifupdown; but that's incidental.
/etc/resolvconf/interface-order: unchanged; contains lo interfaces, then tun, tap, hso, em, p, and eth, ath, then wlan and ppp.

This is straight-out a bug in the patch that assumes *UP* for unmanaged
interfaces. Maybe that patch ought to be dropped by now, but it at the
very least needs to be updated to take into account changes to how DNS
updates are being done now; it's probably a simple matter of checking
whether the NMDevice is unmanaged at the point at which DNS is about to
be changed; but there might still be the issue of reverting to the
original data.

Totally reproduceable on my system --> Triaged, because the next steps
are pretty obvious.

** Changed in: resolvconf (Ubuntu)
       Status: Incomplete => Triaged

** Changed in: resolvconf (Ubuntu)
   Importance: Undecided => High

-- 
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/1023486

Title:
  Cannot resolve domain names if eth0 is in /etc/network/interfaces

Status in “resolvconf” package in Ubuntu:
  Triaged

Bug description:
  I installed two systems with Quantal via a preseed. After booting,
  neither of them could connect to the web. A workaround was to remove
  the eth0 section from /etc/network/interfaces (which the preseed
  added). This is the interfaces file before:

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  After restarting network-manager service it worked again immediately.

  It was also suggested that the state of resolv.conf on the system
  might be a problem:

  nameserver 209.6.3.210
  nameserver 127.0.0.1
  search lexenab

  Removing nameserver 127.0.0.1 and restarting networking/resolvconf and
  network-manager seemed to fix it.

  (having looked at the resolv.conf file after it worked again the
  127.0.0.1 is back, which is interesting)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.4.0+git201206081144.2efeac8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic x86_64
  ApportVersion: 2.3-0ubuntu4
  Architecture: amd64
  Date: Wed Jul 11 11:41:31 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120711.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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