Fully qualified service name in Swarm?

A customer’s network resolved the hostname social to social.mycorp.com.

Inside our container, our service social resolved to their IP rather than the VIP of the service.

I was a bit surprised actually that the Docker DNS didn’t have priority.

In any event, how to fully qualify the service name inside the swarm to avoid this kind of clash?

Inside a container “servicename.networkname” should work.
Each network has its own “DNS-Server”.

1 Like

Works, need to use the full name of the network as seen in docker network ls

Thanks!