/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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023486
Title:
Cannot resolve domain names if eth0 is in /etc/network/interfaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1023486/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
