[Bug 1000244] Re: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package

[Thomas Hood]

@Solomon: Linode tech support has told me that Linode intentionally
removed the /etc/resolv.conf symlink.  By default, all of their
distribution templates use DHCP to obtain the IPv4 address on the first
boot; dhclient is configured to write out a valid resolv.conf file at
/etc/resolv.conf. That's it.

Was the only problem you had the fact that you got an error message?  If
so then the problem is only the word "Error" which should have been
"Warning"; and this problem has already been fixed in Quantal.

In more detail: In Precise, /sbin/resolvconf aborted with an error
message

    resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing
anything.

if /etc/resolv.conf was not a symlink.  In Quantal /sbin/resolvconf
doesn't print that message and does not abort.  However, unless you set

    REPORT_ABSENT_SYMLINK=no

in /etc/default/resolvconf, the warning message

    /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a
symbolic link to /run/resolvconf/resolv.conf

gets printed by the resolvconf update script
/etc/resolvconf/update.d/libc.  So an admin who wants to eliminate the
/etc/resolv.conf symlink and keep resolvconf installed will also have to
set REPORT_ABSENT_SYMLINK=no in order to silence the unwanted warning
message.

-- 
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:
  /etc/resolv.conf symlink does not exist after initial installation of
  resolvconf package

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