Comment 15 for bug 924734

Revision history for this message
Thomas Hood (jdthood) wrote :

I wrote comment #14 before seeing your comment #13. In comment #13 you show that after reboot resolv.conf is not empty. Good. What resolv.conf contains is "nameserver 127.0.0.1". That is correct, assuming you are running a local forwarding nameserver, which is generally dnsmasq — either the NetworkManager-controlled instance of dnsmasq (which listens at 127.0.0.1 in Ubuntu 12.04 but at 127.0.1.1 in 12.10) or the "server" dnsmasq instance started by the "dnsmasq" package (which by default listens at 127.0.0.1 and at all other IP addresses on local network interfaces).

Perhaps dnsmasq is not working properly on your machine. See if the following helps. First, if you are not using the dnsmasq server and the "dnsmasq" package is installed then "sudo apt-get purge dnsmasq". Second, if the "network-manager" package is installed, "sudo gedit /etc/NetworkManager/NetworkManager.conf" and comment out the line "dns=dnsmasq" (but a '#' at the beginning of the line), then save and "sudo service network-manager restart". After this, remote nameserver addresses should appear in resolv.conf and the glibc resolver will contact those external addresses instead of the local forwarding nameserver.