Hi Maxim, Thanks for the reply. What about if we used a stream/tcp proxy_pass with resolver? Something like this: resolver 8.8.8.8 8.8.4.4 ipv6=off; stream { server { listen localhost:81; set $upstream_host my.upstream-host.com; proxy_pass $upstream_host:443; } } server { listen 80; location ~ /api/ { rewrite /api/(.*) /$1 break; proxy_sslby user384829 - Nginx Mailing List - English
Hi Maxim, OK thanks for the reply but how do I resolve this? Am I supposed to use upstream blocks with hostnames in them? My impression is that these won't be resolved inline with the TTL.by user384829 - Nginx Mailing List - English
Hi, I am wanting to resolve upstream hostnames used for proxy_pass inline with the TTL of the DNS record but when I add this configuration the response from nginx is MUCH slower. I've run tcpdump and the upstream DNS record is be resolved and reresolved as TTL would dictate. But requests are slower even when the TTL has not expired and nginx is not attempting to resolve the record. The diffeby user384829 - Nginx Mailing List - English
Did anyone have a solution for this? I also have many of these errors logged because I am using Google Container Engine that does not support IPv6.by user384829 - Nginx Mailing List - English