Thanks for the hint! I haven't worked with domain names in proxy_pass before
and was sure that they're resolved dynamically. I changed the config to:
set $upstream_var example.com;
proxy_pass https://$upstream_var;
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,291252,291286#msg-29128
Hello!
On Wed, Apr 14, 2021 at 01:19:08PM -0400, kay wrote:
> Here is an example of the proxy_pass config, we don't use IP's
>
> proxy_pass https://example.com;
>
> When "example.com" changes the IP address, it is not reflected in nginx.
> We're using k8s pods. Sometime one or two pods have sta
Probably I also need to mention that "example.com" has more than one IP
address (in our case 2)
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,291252,291256#msg-291256
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/l
Here is an example of the proxy_pass config, we don't use IP's
proxy_pass https://example.com;
When "example.com" changes the IP address, it is not reflected in nginx.
We're using k8s pods. Sometime one or two pods have stale DNS cache. Other
pods work fine...
Posted at Nginx Forum:
https://for
W dniu 14.04.2021 o 18:48, kay pisze:
> We tested with a default "resolver 8.8.8.8;" and "resolver 8.8.8.8 30s;"
> options. Both keep using the outdated IP address until you run "nginx -s
> reload". The upstream is AWS LoadBalancer, which changes IPs quite
> frequently.
>
> I'm using nginx 1.19.3.
Hi,
On Wed, Apr 14, 2021 at 12:48:52PM -0400, kay wrote:
> We tested with a default "resolver 8.8.8.8;" and "resolver 8.8.8.8 30s;"
> options. Both keep using the outdated IP address until you run "nginx -s
> reload". The upstream is AWS LoadBalancer, which changes IPs quite
> frequently.
>
> I'm
We tested with a default "resolver 8.8.8.8;" and "resolver 8.8.8.8 30s;"
options. Both keep using the outdated IP address until you run "nginx -s
reload". The upstream is AWS LoadBalancer, which changes IPs quite
frequently.
I'm using nginx 1.19.3. Any clue what could be wrong?
Posted at Nginx Fo
