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

[Thomas Hood]

Initially eth0 was defined in /etc/network/interfaces.  Normally in
/etc/NetworkManager/NetworkManager.conf there is

    [ifupdown]
    managed=false

which causes NetworkManager not to touch eth0.  When you removed the
eth0 section from /e/n/i and restarted network-manager, NetworkManager
took control of eth0, configured it and obtained nameserver addresses
from the DHCP server.  Somehow the addresses then got into resolv.conf
but it isn't clear to me that this was done in the right way.

Please submit the output of the following commands run in a terminal.

    cat /etc/resolv.conf
    ls -l /etc/resolv.conf
    sudo lsattr /etc/resolv.conf
    ls -l /run/resolvconf
    ls -l /run/resolvconf/interface
    for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done
    ls -l /etc/resolvconf/resolv.conf.d
    for F in /etc/resolvconf/resolv.conf.d/* ; do echo === $F === ; cat $F ; done
    ls -l /etc/resolvconf/interface-order
    cat /etc/resolvconf/interface-order

** Package changed: network-manager (Ubuntu) => resolvconf (Ubuntu)

-- 
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:
  Incomplete

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