Host DNS search domain is not propagated to minikube DNS

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Minikube version (use minikube version): v0.20.0

Environment:

• OS (e.g. from /etc/os-release): Windows 7
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualbox
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): file://C:/cygwin64/home/b26978/.minikube/cache/iso/minikube-v0.20.0.iso
• Install tools:
• Others:

What happened: When I create a new minikube using minikube start the DNS configuration inside the minikube VM doesn't use the same DNS search domain as the host uses. I'm behind a corporate firewall and the proxy hostname isn't resolvable from inside the VM, thus the http_proxy and https_proxy settings are useless.

Apparently the DNS system is managed by systemd-resolved, and the configuration file at used is located at: /etc/systemd/resolved.conf. The Domains settings inside is commented in my configuration. I managed to get the DNS (and proxy) working by setting the Domains value in the /etc/systemd/resolved.conf and restarting the service:

systemctl daemon-reload
systemctl restart systemd-resolved

Sadly, I'm not fluent in Go and I'm not able to submit a patch to fix the issue.

What you expected to happen: The configuration file (/etc/systemd/resolved.conf) contains the Domains settings and it's set to the correct value.

How to reproduce it (as minimally and precisely as possible): Set the DNS domain search to something (non empty) under Windows 7. Create a new minikube vm using minikube start.

Anything else do we need to know: