Comment 1 for bug 1032855

This is nothing to do with resolvconf. dhclient itself updates /etc/resolv.conf when it receives DNS information from DHCP; and so does Network Manager. The point of having resolvconf as part of the base system in Ubuntu is precisely that all the network management tools want to be able to provide dynamic DNS information, and resolvconf is the first standard framework to let users control this *without* having to chase down half a dozen scripts.

Far from being a "minimum breakage path", replacing the /etc/resolv.conf file with a symlink means you now don't benefit from the (recommended) resolvconf framework.

A more effective way to manage this is by creating /etc/resolvconf/resolv.conf.d/head with your preferred nameserver information. resolvconf knows that ::1 is special and won't include any other dynamic nameserver information.