Lubuntu upgraded to 12.10 from 12.04 DNS not working

[SwiftPengu]

Hello, I upgraded my Lubuntu 12.04 (which was working fine) to 12.10 today and I've encountered the following problem:

DNS does not seem to be working correctly, it looks like the DNS settings I set in Network-Manager are not saved/used correctly.

If I type

nslookup www.google.com

in a terminal window I get a timeout.

If I type

nslookup www.google.com 8.8.8.8

in a terminal window I get a response.

Everything dependent on DNS is not working (firefox etc.)

It thought my router might be the culprit because sometimes DNS fails using the router, however if I type

nslookup www.google.com a.b.c.d

(router ip) I get replies.

Anyway, I tried to change the DNS address in the network-manager configuration to 8.8.8.8 with DHCP enabled for the IP-address.
After reconnecting/rebooting nslookup shows the same behaviour.

I've found some info on the internet mentioning dnsmasq which might cause trouble:
https://bugs.launchpad.net/ubuntu/+s...r/+bug/1031350

However, I am not sure if this is the problem in my case because I do have the dnsmasq.d folder mentioned in the bug report.

Does somebody have an idea of what might be wrong?

[SwiftPengu]

As a temporary fix I was able to install wicd from the 12.04 repositories, and update it to the 12.10 version with my renewed connection.

I needed at least the following packages (I tried sudo apt-get build-dep on a ubuntu 12.04 install, and then obtained the remaining packages):
-po-debconf
-python-wicd
-wicd-daemon
-wicd-gtk

[yngvewb]

I have the same problem after upgrading Lubuntu to 12.10. Could you pleace describe in more detail how you resolved the issue? Thanks

[SwiftPengu]

Hi, unfortunately I cannot be very precise. What I did was as follows:

1.Boot into my ubuntu 12.04 install
2.Run

sudo apt-get build-dep wicd

3.Do not install anything (by selecting no when asked), but note the package names mentioned under "the following packages will be installed"
4.Use

sudo apt-get download [package name] [package name]

to obtain the .deb files for those packages
5.Boot into Lubuntu and try to install all the .deb files
6.Note any missing packages (in my case the aforementioned 4 packages)
7.Boot back in to ubuntu and download the missing packages too
8.Boot into Lubuntu and install the new packages

9.From this point it worked on my end and installed wicd instead of network-manager-gnome

The reason I cannot be very specific on the packages needed is because I used two systems with random extra software installed, so you might also need e.g. build-essentials.

Also be aware of the fact that this is only a temporary solution as this does not fix any problems but only replaces a misbehaving network manager with a different one.

[darkod]

When you set it manually in the connection options it should work. Are you sure you configured it correctly?

Also, did you change the option to Automatic (address only)? That is needed so that it accepts the manual entries for DNS servers.

PS. And, which is always a good idea, you don't have to upgrade to a new version the first day it comes out. Wait and see if people start reporting issues with it. Besides, running 12.04 which is LTS and has 5 years support, I don't understand why are you upgrading to 12.10 which has only 18 months of support anyway. Unless it has some options that you can't install or add to 12.04 (which is very rare), you don't even need to upgrade ever.

[kevinbeard]

Looks like this is a known issue. The instructions here worked for me:

https://bugs.launchpad.net/ubuntu/+s...r/+bug/1051348

[SwiftPengu]

I reinstalled gnome-network-manager and removed (not purged) wicd.
My DNS is now resolving, so it might be that this had been fixed.

My /etc/resolv.conf is saying this, which is the same as it said with wicd:

domain lan
search lan
nameserver 192.168.1.254

Which points to my router (dns forwarder), however in my settings
I am using 8.8.8.8 (google dns for testing), and nslookup reports not using 8.8.8.8 but 192.168.1.254:

me@PC:~$ nslookup www.google.com
Server:		192.168.1.254
Address:	192.168.1.254#53

Non-authoritative answer:
Name:	www.google.com
Address: 173.194.66.103
Name:	www.google.com
Address: 173.194.66.105
Name:	www.google.com
Address: 173.194.66.147
Name:	www.google.com
Address: 173.194.66.99
Name:	www.google.com
Address: 173.194.66.106
Name:	www.google.com
Address: 173.194.66.104

My Network-Manager configuration is as follows:


I am thinking I am now still using my old wicd config file (I have already rebooted), and somehow it is still not overwritten.
I will try the symlink mentioned in the launchpad bug report tomorrow.

[SwiftPengu]

Since the last time I replied here, I noticed the following things:
1.If I edit /etc/resolv.conf and put the DNS server I want to use there, it is used.

2.After symlinking /run/resolvconf/resolv.conf to /etc/resolv.conf
my system uses the NetworkManager settings

sudo mv /etc/resolv.conf /etc/resolv.conf.bak
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf

[jdthood]

Since the last time I replied here, I noticed the following things:
1.If I edit /etc/resolv.conf and put the DNS server I want to use there, it is used.

So to begin with /etc/resolv.conf was a plain file.

2.After symlinking /run/resolvconf/resolv.conf to /etc/resolv.conf
my system uses the NetworkManager settings

sudo mv /etc/resolv.conf /etc/resolv.conf.bak
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf

Having created this symlink you have given control of /etc/resolv.conf back to resolvconf which NetworkManager uses for maintaining resolv.conf contents. Keep it this way. Resolvconf is now part of the Ubuntu base system and is expected to be present. If resolvconf does not seem to be working properly in some instance then report a bug against the resolvconf package and we will investigate the issue with you.

[Androzani1]

I had a similar problem on Windows XP. When the DNS WAS working, I copied it onto notepad. I then tweaked the settings to always use that DNS, rather than finding it automatically. If you can do something similar on Lubuntu, it may fix it.