Closed mcblum closed 5 years ago
@mcblum are you specifying any extra DNS arguments
Do you have a search domain in your /etc/resolv.conf
, if yes then the ndots:0
will not append the name and search in that domain which might cause your internal DNS names to fail
@arkodg the nodes needed a restart for some reason. I know... so simple.
Expected behavior
That the Swam DNS server used in the overlay network would forward requests on.
Actual behavior
Even though the host can resolve domain names correctly, the container cannot.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.) We're running our own swarm for a dev environment, and after a few days of working on this I can't figure out how to get it to work. One of our Node services requires a connection to MongoAtlas, and I cannot resolve the DNS entry for it. Looking at the logs, it appears that every once in a while it does actually resolve, which is very weird.
Running
nslookup google.com
inside the container gives meresolv.conf:
If anyone has any idea what's happening here, I've been at this since Sunday and just cannot figure it out. I've also tried multiple different base images, installing different things during the build, pretty much anything I can think of.
Thank you!