You can try to use this module to resolve the DNS ;)
https://github.com/GUI/nginx-upstream-dynamic-servers
On Wed, Mar 16, 2016 at 1:34 PM, Valentin V. Bartenev
wrote:
> On Friday 11 March 2016 07:01:49 Frank Liu wrote:
> > Hi Valentin,
> > Thanks for clearing up . I was looking at the wrong mod
On Friday 11 March 2016 07:01:49 Frank Liu wrote:
> Hi Valentin,
> Thanks for clearing up . I was looking at the wrong module.
> Do you have any comments to the other two questions?
1. That will result in "502 Bad Gateway" response, and corresponding
message will be written to error_log.
2.
Hi Valentin,
Thanks for clearing up . I was looking at the wrong module.
Do you have any comments to the other two questions?
Frank
On Friday, March 11, 2016, Valentin V. Bartenev wrote:
> On Thursday 10 March 2016 14:55:06 Frank Liu wrote:
> > Hi,
> >
> > I saw this example at serverfault.com:
On Thursday 10 March 2016 14:55:06 Frank Liu wrote:
> Hi,
>
> I saw this example at serverfault.com:
>
> server {
> ...
> resolver 127.0.0.1;
> set $backend "http://dynamic.example.com:80";;
> proxy_pass $backend;
> ...
> }
>
> I have a few questions:
> 1) If the resolver DNS
On 3/11/16 12:47 PM, B.R. wrote:
[...]
> 3) This
> page http://nginx.org/en/docs/stream/ngx_stream_core_module.html#resolver
> says "This directive is available as part of our commercial
> subscription.". Is that still up to date? Can "resolver",
> "resolver_timeout" be used in
On Thu, Mar 10, 2016 at 11:55 PM, Frank Liu wrote:
> server {
> ...
> resolver 127.0.0.1;
> set $backend "http://dynamic.example.com:80";;
> proxy_pass $backend;
> ...
> }
>
> I have a few questions:
> 1) If the resolver DNS becomes unavailable (say connection timeout), what
>
Hi,
I saw this example at serverfault.com:
server {
...
resolver 127.0.0.1;
set $backend "http://dynamic.example.com:80";;
proxy_pass $backend;
...
}
I have a few questions:
1) If the resolver DNS becomes unavailable (say connection timeout), what
will nginx do? Will it keep
