Re:Docker 1.10.0 is out
by falcolas on Thursday February 04, 2016 @06:31PM
(#11038125)
I tend to agree with you. Between time to live, caching, and various namespace conflicts, this could make for a very large troubleshooting headache.
[ Parent
| on HN ]
Docker assumes it cannot trust the container's DNS resolver to respect TTL and cache in a compliant way. So it guarantees stable name->ip mapping for each container. As a result, when you point a service endpoint at another container, it's the IP/container mapping that is changed, which is a much more reliable and atomic change. I would definitely never rely on changing DNS records to orchestrate changes to my production stack, that would be way too brittle.