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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177746 Title: resolv.conf is a dangling link after every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1177746/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
