[Bug 1177746] [NEW] resolv.conf is a dangling link after every reboot
latimerio
1177746 at bugs.launchpad.net
Wed May 8 11:25:26 UTC 2013
Public bug reported:
I administer > 100 linux systems, most of them 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 of 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 anymore.
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 1 machine with latest ubuntu 12.04.02 LTS
I don't see this a duplicate of 366967.
** Affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
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 > 100 linux systems, most of them 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 of 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 anymore.
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 1 machine with latest ubuntu 12.04.02
LTS I don't see this a duplicate of 366967.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1177746/+subscriptions
More information about the foundations-bugs
mailing list