resolv.conf is a dead link after upgrade to Maverick

[dm]

Binary package hint: resolvconf

After upgrading to Maverick the '/etc/resolv.conf' file is a dead link.
'/var/run/resolvconf' does not exist. After dpkg-reconfigure 'resolvconf' this directory will be created.
After restarting the /etc/init.d/networking the file 'eth1.inet' in /var/run/resolvconf/interface exists but not the file '/var/run/resolvconf/resolv.conf' so that the link '/etc/resolv.conf' is dead as before. After doing a reboot the dirs and files in '/var/run' concerning 'resolvconf' are lost again. So it is not possible to use the resolvconf to configure a simple network with static IP and DNS. I think the whole behavior and setup of resolvconf is a terrible thing. I've never used a really proper working version of this package which works on all of my Linux installations at my job (static Ip, static DNS), at home (home LAN with static IP and DNS) and on my notebook (networkmanager, dynamic IP and DNS). The job of the resolvconf package sounds really simple on paper but it is sad in praxis. After every Ubuntu upgrade I run in the same failures - no X, no net. Why? What should do a simple man who wants only to use it to work? I have some experiences in Linux especially in Ubuntu and I know what to do. But other people? I can't suggest Linux to such a simple user. I use Linux at work for over 3 years, when will it be done?

Jan

[Thomas Hood (jdthood)]

A new Ubuntu resolvconf package has been prepared by the Debian maintainers which we hope will fix this bug.

I ask you to test this new package before we upload it to the Ubuntu repos.

Please install the resolvconf package from ppa:jdthood/resolvconf (https://launchpad.net/~jdthood/+archive/resolvconf) and let me know whether or not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
<email address hidden>

[latimerio (fomember)]

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 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 but the problem is still there.
What is the best way to get rid of this whole mess and have properly running systems again?

[Thomas Hood (jdthood)]

The best solution is for your employer to hire a competent person to administer the 100+ Linux systems. Competences of the candidate should include the ability to debug Linux machines while remaining calm and not immediately resorting to whinging in the logs of bug reports closed two years ago. Another important asset would be the ability to remember having installed third-party software or having added custom scripts to do ugly things to resolv.conf which could later interfere with the correct functioning of systems upgraded to Ubuntu 12.04.