I also don't have the option of using the magical DNS name, because I need a DNS name that resolves both inside the docker container, and in locally running scripts. The solution of adding an extra_hosts entry cannot be applied to all of my use-cases (in some cases, the compose file is not mine to manipulate). In fact, resolution of the magical DNS name fails if I configure the docker daemon dns in this fashion. As others have experienced, this doesn't seem to help. I tried configuring the docker daemon dns setting to be my domain DNS server, which knows how to resolve my local host's fully qualified DNS name. Reset to factory defaults (as described here: ) also did not help. I've had the same experience with Docker Desktop for Windows versions 2.1.0.1 and 2.1.0.3. Check that busybox not have the same DNS ip address that is setted in DNS configuration in Dockerīut, if I set -dns option with docker run command, the result is the same,Īlso, if I change the daemon configuration in Docker, same result, see the following images: Apply fixed DNS configuration and restart Docker.If I set the DNS configuration fixed in Docker, the result is the same. The ip address that appears as nameserver in /etc/nf is assigned automatic by Docker according to Network settings. Get valid ping or nslookup response using busybox docker image Actual behavior Windows Version: Windows build 17763.379.I have tried with the latest version of my channel (Stable or Edge).

Same behavior as I upgraded to 2.1.0.0 today.

Docker network dns