Comment 2 for bug 1480263

This change is breaking deployments. Specifically it prevents MAAS from being able to download images since it is unable to resolve maas.ubuntu.com once the original nameserver is removed.

There is also possibly a bug with how we are using the local datasource with cloud-init to configure networking since on reboot /e/n/i is always overwritten with the contents of the metadata section in the local datasource. We will also need a more intelligent way to work out what nameservers are configured and on what interface(s) and apply then accordingly with e.g.

echo "nameserver 127.0.0.1"| sudo resolvconf -a eth0.inet

So, i'm going to revert this for now until we find a better solution.