From my experience I’ve not had any issues with Caddy using stale DNS entries when proxying Docker containers. From the forums it looks like Caddy doesn’t expl

From my experience I’ve not had any issues with Caddy using stale DNS entries when proxying Docker containers. From the forums it looks like Caddy doesn’t explicitly define any DNS behaviour, it relies on Golangs defaults, which in turn simply uses whatever the host provides. I.e. whatever IP your host DNS resolution returns is used, and Caddy doesn’t cache internally, it relies on your hosts DNS cache. It’s reasonable to assume that any modern OS respects DNS TTL, and for something like Docker it’s gonna be doing a lookup on every request (which should be pretty much instant, as everything is on the same machine). https://caddy.community/t/proxy-dns-resolver-mechanism/5934 https://caddy.community/t/proxy-dns-resolver-mechanism/5934 https://stackoverflow.com/questions/40251727/does-go-cache-dns-lookups#40252460 https://stackoverflow.com/questions/40251727/does-go-cache-d...