To me it seems that the problem is that the update-resolv-conf script was designed to work with pure dnsmasq and not systemd-resolved (used since 16.10).
I googled around and found somebody has made an update-systemd-resolved script to replace the update-resolv-conf script when systemd-resolved is in play.
Jordi:
To me it seems that the problem is that the update-resolv-conf script was designed to work with pure dnsmasq and not systemd-resolved (used since 16.10).
I googled around and found somebody has made an update- systemd- resolved script to replace the update-resolv-conf script when systemd-resolved is in play.
See my detail explanations here: https:/ /bugs.launchpad .net/ubuntu/ +source/ systemd/ +bug/1624317/ comments/ 42
I works well for me at least.