Comment 1 for bug 926447

I can confirm it here so marking as Critical but not marking as Triaged just yet as I'm unsure it's resolvconf's fault.
It may instead be netcfg's or another d-i component touching /etc/resolv.conf

Resolvconf's behavior at install time is:
 - Move current resolv.conf to /run/resolvconf/resolv.conf
 - Make relative symlink from /etc/resolv.conf to ../run/resolvconf/resolv.conf

But the above happens during debootstrap so it's probably not what you see. The rest of resolvconf is either trigger by ifupdown, dhclient, network-manager or init but none of these should be running in the install target (or something else is clearly wrong).

I'll try to spend some time this weekend testing this as it's making some of my automated installs (all of these depending on network) fail, not to mention other people's ;)