Comment 19 for bug 1671606

The change introduced[1] in resolveconf-1.78ubuntu4 over 1.78ubuntu2 affects *when* resolvconf service starts; but does not affect the runtime code and is not involved in any of the runtime action of the resolvconf service. I'm marking the resolvconf task as invalid.

If you feel that the resolvconf change to when resolvconf service starts during boot affects the runtime DNS settings, please do re-open against resolvconf and include:
a. systemctl status resolvconf
b. contents of /etc/resolv.conf

1. diff -Nru resolvconf-1.78ubuntu2/debian/resolvconf.service resolvconf-1.78ubuntu4/debian/resolvconf.service
--- resolvconf-1.78ubuntu2/debian/resolvconf.service 2015-06-03 15:58:21.000000000 -0500
+++ resolvconf-1.78ubuntu4/debian/resolvconf.service 2016-12-07 03:03:18.000000000 -0600
@@ -2,7 +2,8 @@
 Description=Nameserver information manager
 Documentation=man:resolvconf(8)
 DefaultDependencies=no
-Before=networking.service
+Before=network-pre.target
+Wants=network-pre.target