Access container by hostname on internal Rancher network

If that other container belongs to the same stack that the container you are trying to resolve belongs to? Containers are resolvable to other containers only within the same stack

I see. I can confirm this part works. curling any container from another container within the stack by container name does work as expected.

I think I may have misunderstood the changes brought in by 0.46 to mean that all containers would be discoverable with all other containers.

Is there to specify that a container is resolvable from anywhere else within the managed network?

Thanks for providing the further insights into resolv.conf and answers.json. Is the Rancher DNS server always at 169.254.169.250?