Network-manager 0.6.5 replaces /etc/resolv.conf (should stay a symlink)
Bug #121708 reported by
Mephisto
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
NM 0.6.5 (as found in gutsy) no longer works with resolvconf, because it replaces the symlink /etc/resolv.conf with a regular file. With this, it bypasses resolvconf completely and on my vpn network this breaks dns. I get dns servers from the access point, and then have to connect to a vpn, after which i end up with an empty /etc/resolv.conf. Resolvconf used to handle this properly. This worked fine with 0.6.4.
To post a comment you must log in.
Generally it seems like a bad idea to fiddle with /etc/resolv.conf.
I run pdnsd which I recommend every user for breaking-through surfing speed especially if you connect on a WLAN router.
PLEASE leave that file alone, if networkmanager needs to setup a DNS (which might be a good idea) let it depend on pdnsd and change the config file for that package instead!!