It seems the problem is actually caused by the true default answer to the resolvconf/link-tail-to-original question. Without it, the host's original /etc/resolv.conf is still preserved as /etc/resolvconf/resolv.conf.d/original, but resolv.conf.d/tail is NOT linked to it, so it never ends up in the /etc/resolv.conf produced by resolvconf.
I've found a comment by jdthood (resolvconf's maintainer) that the resolvconf/link-tail-to-original should default to false and is a candidate for removal in a future version of resolvconf: https://bugs.launchpad.net/ubuntu-business- remix/+bug/1063639/comments/16 It seems this still isn't the case, as the latest resolvconf still contains the true default answer: http://packages.ubuntu.com/trusty/resolvconf Interestingly, the "ubuntu" branch of the Debian resolvconf git repo has always contained a false answer for that question: http://anonscm.debian.org/gitweb/?p=resolvconf/resolvconf.git;a=shortlog;h=refs/heads/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279760 Title: Take into account the debotstrapped environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1279760/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
