[Bug 1177746] Re: resolv.conf is a dangling link after every reboot

[Thomas Hood]

Thanks for the report.

Resolvconf works properly on fresh installation of Ubuntu 12.04 and
later and on most machines upgraded from earlier versions of Ubuntu.
That it does not work on your machines indicates that there is something
special about your configuration.

It would be useful to know whether (1) resolvconf fails to generate
/run/resolvconf/resolv.conf at boot time, or (2) something deletes
/run/resolvconf/resolv.conf after resolvconf has generated it at boot
time.

Are you using genuine Ubuntu or a derivative?

Do you have any local custom scripts that run at boot time which touch
resolv.conf?

Do you use a third-party VPN client?

Regarding the question of whether or not the resolver should be
dynamically configured...  It is simply a fact that the list of
available nameservers, and information about those nameservers, changes
dynamically. So either the resolver has to be dynamically reconfigured
or it has to be configured to forward queries to a forwarding nameserver
that is dynamically configured. (Before the advent of resolvconf many
other utilities overwrote /etc/resolv.conf... in a totally uncoordinated
way.)

-- 
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/1177746

Title:
   resolv.conf is a dangling link after every reboot

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  I administer more than 100 Linux systems, most of which are desktops
  with more than 1 nic and running Ubuntu LTS. With the advent of 12.04
  our static resolv.conf got replaced by the resolvconf / network-
  manager thing and it causes only trouble. After every reboot
  /etc/resolv.conf is a dangling link pointing to
  ../run/resolvconf/resolv.conf which does not exist.

  I have uninstalled network-manager and resolvconf and reinstalled
  them, run dpkg-reconfigure resolvconf and resolvconf --enable-updates,
  did ifdown and ifup on my primary interface and it looks fine.

  But after a reboot the problem is there again: resolv.conf points to a
  non-existing target! Thus those machines cannot access the network any
  more.

  What is the best way to get rid of this whole mess and have properly
  running systems again?

  I don't see any reason why a desktop should dynamically configure the resolver.
  Maybe the maintainer should add a check and leave desktops untouched?

  As this bug affects more than one machine with latest Ubuntu 12.04.02
  LTS I don't see this as a duplicate of bug #366967.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1177746/+subscriptions