broken dns resolving options in /etc/resolv.conf upon startup

[Anton Kudris]

After upgrading to Ubuntu 10.10 (from 10.04) I've got very nasty bug upon every loading of my desktop: the dns resolver doesn't work. My laptop is connecting to wireless router and receives settings using DHCP.
After upgrade I first discovered that my browser can't open almost any web site (in fact I could be able to open some sites... ). Messengers (Empathy and Skype) also couldn't connect. So I started digging and found that my /etc/resolv.conf looks like this:

# Generated by Connection Manager
options edns0
nameserver 192.168.1.1

Now name server is ok - that's my router. But I have no idea what is edns0 option... When I removed "options edns0" everything get back to normal. I was able to browse inet/chat etc

but every time I reboot my laptop -- that nasty option return to resolv.conf and I have to manually delete it

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Oct 20 20:46:34 2010
IpRoute:
 192.168.1.1 dev wlan0 scope link
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.182
 default via 192.168.1.1 dev wlan0
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: network-manager
WpaSupplicantLog:

[Victor Vargas (kamus)]

Have you checked if there is a malformed option set in your wireless router? with other computers DHCP is working fine?

[Dennis Schridde (devurandom)]

(In reply to comment #2)
I have the very same problem at home (FritzBox router) and in the university (Cisco/RADIUS/... network). dhcpcd3 does not set resolv.conf, but dhclient does. It is a regression from Ubuntu 10.04.

[Dennis Schridde (devurandom)]

P.S: I just notice this bug is not against wicd/dhcpcd3, so I add this note:
I am using wicd (not network-manager) and by default that one uses dhcpcd3 as DHCP client. In the configuration of wicd, choosing dhclient explicitly instead of "default" or dhcpcd will set resolv.conf correctly.

[Mathieu Trudel-Lapierre (cyphermox)]

Dennis, please open a separate bug for this, it seems to me like it's a different issue (the original reporter says nothing of dhcpcd, and the logs don't contain anything about it). Once done, report back the bug number here so we can look into it.

Anton, could you please try with default settings for the wireless network and check if things work fine? You might also want to check whether trying with your custom settings in /etc/network/interfaces removed it works properly.

Thanks,

[Joshua Lückers (joshualuckers)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[Dennis Schridde (devurandom)]

> Dennis, please open a separate bug for this, it seems to me like it's a different issue (the original reporter says nothing of
> dhcpcd, and the logs don't contain anything about it). Once done, report back the bug number here so we can look into it.
Opened it as bug #664839