October 31, 2017 01:26PM
Thank you for your replies. I think we have found the root cause. We have found below:

When you are using variables in a proxy_pass directive, nginx will use runtime resolving except if :
the target server is declared as an IP address
the target server name is part of an upstream server group
the target server name has already been resolved (e.g. it matches a server name in another server block)

In our case we have one server block, with default set. Apache is sending server name as legacy.domain.com and nginx also proxying to legacy.domain.com, so I belive because both server name and proxy host is same, nginx not trying to re-resolve the ip address.
Subject Author Posted

Resolver not re-resolving new ip address of an AW ELB

RKGood October 27, 2017 02:58PM

Re: Resolver not re-resolving new ip address of an AW ELB

RKGood October 27, 2017 03:00PM

Re: Resolver not re-resolving new ip address of an AW ELB

RKGood October 30, 2017 11:54AM

Re: Resolver not re-resolving new ip address of an AW ELB

Nishikubo Minoru October 30, 2017 09:14PM

Re: Resolver not re-resolving new ip address of an AW ELB

pankaj@releasemanager.in October 30, 2017 11:25PM

Re: Resolver not re-resolving new ip address of an AW ELB

RKGood October 31, 2017 01:26PM

Re: Resolver not re-resolving new ip address of an AW ELB

ru@nginx.com November 02, 2017 06:06AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 58
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready