Why can't I access a service by its name from rancher-server container?

Archive Rancher 1.x
1

Hi Guys,

Could anyone explain me why I can’t access any service by its [name].[stack] but only by its IP address from rancher-server container. From other containers service resolution works well.

I just wanted to point Rancher to influx DB by providing service name instead of the IP address as recommended here

2

Those names are provided by a DNS server running in the network agent containers on each host. The server container points at your regular public DNS.

3

Thank you for your reply. Could you please explain the idea behind this difference?

4

General chicken and egg problems… The server may need to resolve things during startup, the server container doesn’t generally manage itself, and it is not part of the overlay network so none of the IP 10.42 addresses would be reachable anyway.

5

Vincent, thank you for the explanation.