[GH-ISSUE #190] Unable to recover Docker hostnames by DPS (Windows 10 Pro) #74

New issue

Closed

opened 2026-02-26 04:33:58 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 04:33:58 +03:00

Owner

Originally created by @kwanhs on GitHub (Jan 31, 2020).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/190

On a Windows 10 Pro, I started a docker image of DPS latest (as of 31 Jan 2020) with a few nginx images. Bashing into the DPS image, I could not nslookup or ping the other nginx by their hostnames or docker container names. However, pinging their actual IP works.

How I started DPS:

docker run --name dps --hostname dps -p 5380:5380 -p 53:53/udp defreitas/dns-proxy-server

How I started nginx's.

docker run --name ng1 --hostname nginx.dev.intranet1 -e 'HOSTNAMES=nginx2.dev.intranet,nginx3.dev.intranet' nginx
docker run --name ng2 --hostname nginx.dev.intranet2 -e 'HOSTNAMES=nginx2.dev.intranet,nginx3.dev.intranet' nginx
docker run --name ng3 --hostname nginx.dev.intranet3 -e 'HOSTNAMES=nginx2.dev.intranet,nginx3.dev.intranet' --dns=172.17.0.2 nginx

I further connected all of them to a user-defined bridge network.

Examples of failed nslookup requests from the DPS bash:

root@dps:/app# nslookup ng3
Server: 172.17.0.2
Address: 172.17.0.2#53
** server can't find ng3: NXDOMAIN

root@dps:/app# nslookup nginx.dev.intranet1
Server: 172.17.0.2
Address: 172.17.0.2#53
** server can't find nginx.dev.intranet1: NXDOMAIN

However, within the same ng container, it can ping or nslookup itself by both its container name and hostname. But it fails to ping/nslookup others.

The above problems was replicated in another Windows 10 Pro.

Originally created by @kwanhs on GitHub (Jan 31, 2020). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/190 On a Windows 10 Pro, I started a docker image of DPS latest (as of 31 Jan 2020) with a few nginx images. Bashing into the DPS image, I could not nslookup or ping the other nginx by their hostnames or docker container names. However, pinging their actual IP works. How I started DPS: > docker run --name dps --hostname dps -p 5380:5380 -p 53:53/udp defreitas/dns-proxy-server How I started nginx's. >docker run --name ng1 --hostname nginx.dev.intranet1 -e 'HOSTNAMES=nginx2.dev.intranet,nginx3.dev.intranet' nginx docker run --name ng2 --hostname nginx.dev.intranet2 -e 'HOSTNAMES=nginx2.dev.intranet,nginx3.dev.intranet' nginx docker run --name ng3 --hostname nginx.dev.intranet3 -e 'HOSTNAMES=nginx2.dev.intranet,nginx3.dev.intranet' --dns=172.17.0.2 nginx I further connected all of them to a user-defined bridge network. Examples of failed nslookup requests from the DPS bash: > root@dps:/app# nslookup ng3 Server: 172.17.0.2 Address: 172.17.0.2#53 ** server can't find ng3: NXDOMAIN >root@dps:/app# nslookup nginx.dev.intranet1 Server: 172.17.0.2 Address: 172.17.0.2#53 ** server can't find nginx.dev.intranet1: NXDOMAIN However, within the same ng container, it can ping or nslookup itself by both its container name and hostname. But it fails to ping/nslookup others. The above problems was replicated in another Windows 10 Pro.

kerem closed this issue

2026-02-26 04:33:58 +03:00

kerem commented

2026-02-26 04:33:58 +03:00

Author

Owner

@kwanhs commented on GitHub (Feb 8, 2020):

Without a response from anyone, I went on for defreitas/dns-proxy-server (https://hub.docker.com/r/defreitas/dns-proxy-server/) with dnsmasq.

I am all good now.

@kwanhs commented on GitHub (Feb 8, 2020): Without a response from anyone, I went on for defreitas/dns-proxy-server (https://hub.docker.com/r/defreitas/dns-proxy-server/) with dnsmasq. I am all good now.

kerem referenced this issue

2026-02-26 04:34:38 +03:00

[PR #74] [MERGED] Fixing wildcard resolution local configuration #256