title: How can I debug Docker name resolution?
body: <p>I have a very peculiar problem regarding Docker and how containers resolve the IP address of other containers using their container names.</p>
  <p>My machine runs many different containers interacting with each other, making the problem difficult to reproduce in a minimal example as would be preferred if possible.</p>
  <p>The problem I am encountering is that whenever I add a new container/service/docker-network (by running <code>docker-compose up</code>) all of a sudden, my container for reverse proxying HTTP(S) traffic starts resolving the IP addresses of containers incorrectly.</p>
  <p>I can verify that the Name --&gt; IP resolutions are incorrect by checking the logs of where the reverse proxy is trying to connect and then running <code>docker network inspect</code> on the container I expect it to resolve. These are now not the same, resulting in errors all around.</p>
  <p>Whenever I stop the new service that triggered the errors, the name resolution is back to normal and all works as expected again. I have encountered this same problem when starting multiple different images, so the problem is most likely not in the new container.</p>
  <p>Since I can not provide you with a simple minimally reproducible example (I would if I could), <strong>how can I further debug the docker name resolution in an attempt at gathering more information about this problem?</strong></p>
  <p>Any advice is appriceated. I know this is not the optimal Stack Overflow question, but I can't do much more without more information about my problem.</p>
  <p>I hope you understand.</p>