/etc/resolv.conf containing 127.0.0.1 was correct, provided you have a
local nameserver running that listens at IP address 127.0.0.1.
In Ubuntu 12.10, the dnsmasq process controlled by NetworkManager
listens at 127.0.1.1, not at 127.0.0.1, so it wasn't NetworkManager that
registered 127.0.0.1 with resolvconf.
My guess is that it was bind9 that did that, and that your problem was
bug #933723.
For background information please read the following blog posting.
https://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1098152
Title:
DNS resolve failed after upgrade from 12.04 to 12.10
Status in “bind9” package in Ubuntu:
Incomplete
Bug description:
I just upgraded from 12.04 to 12.10 and suddenly I couldn't resolve the host.
The ip and DNS was correct.
The nameserver in /etc/resolv.conf was 127.0.0.1. I changed it to the DNS
directly and all went swell.
I had to install dnsmasq for it to work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1098152/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
