[Bug 1000244] Re: resolv.conf not populated because /etc/resolv.conf symlink was not created
Thomas Hood
1000244 at bugs.launchpad.net
Sun Jun 3 02:50:20 UTC 2012
It would be helpful if the administrator's own answer to resolvconf
/linkify-resolvconf were recorded somewhere before the value of the
latter gets reset to false in the postinst.
Better yet, perhaps: Change the postinst so that it doesn't fiddle with
the answer to linkify-resolvconf; instead create a new question,
resolvconf/linkify-done, which gets sets from false to true on
linkification and whose value being true prevents linkification being
repeated on subsequent postinst runs.
Even better would be to return to having an idempotent postinst; but
then another solution would have to be found for the problem that the
debconf-fiddling solved.
Regarding #1000244 itself, we still have the unsolved mystery of how pdf
could clean-install 12.04 and end up with no resolv.conf symlink (see
comment #10).
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
resolv.conf not populated because /etc/resolv.conf symlink was not
created
Status in “resolvconf” package in Ubuntu:
Incomplete
Bug description:
I upgraded an 11.10 install to 12.04, and now I'm unable to resolve
domain names because Network Manager does not populate my
/etc/resolv.conf file.
For example, my local wireless router uses the domain "mylocaldomain"
and nameservers 10.157.10.12 and 10.157.10.14, so in 11.10, after
connecting to the router I would see this in my /etc/resolv.conf:
domain mylocaldomain
search mylocaldomain
nameserver 10.157.10.12
nameserver 10.157.10.14
Now /etc/resolv.conf contains the settings last set before I upgraded
to 12.04, and doesn't update them for whatever network I'm currently
on. I have to manually guess the settings and modify /etc/resolv.conf
in order to resolve domain names.
I believe this may be related to
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922677 and
how the "resolvconf" program has been introduce to manage this. I
believe this is a new bug with how prior installs are improperly
upgraded.
I tried removing the line "dns=dnsmasq" from
/etc/NetworkManager/NetworkManager.conf and then running `sudo restart
network-manager`, but that had no effect.
I tried running `resolvconf --enable-updates` but I get the error
"resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing
anything."
Based on https://help.ubuntu.com/12.04/serverguide/network-
configuration.html#name-resolution, I tried establishing this symlink
myself, but the file /run/resolvconf/resolv.conf does not exist on my
system.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Wed May 16 09:57:25 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
IpRoute:
default via 192.168.1.1 dev eth2 proto static
169.254.0.0/16 dev eth2 scope link metric 1000
192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.205 metric 2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-05-10 (5 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth2 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions
More information about the foundations-bugs
mailing list