dns name for upstream

Wandenberg Peixoto wandenberg at gmail.com
Wed Mar 16 16:41:07 UTC 2016


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 <vbart at nginx.com>
wrote:

> 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. There's the "resolve" parameter of the "server" directive in upstream,
>     but it's available in commercial version only.
>
>     See the docs:
>     http://nginx.org/en/docs/http/ngx_http_upstream_module.html#server
>
>     Back to your first question, this parameter has different behavior,
>     it will preserve the old IPs in case of resolving error.
>
>
>   wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160316/8f217da5/attachment.html>


More information about the nginx mailing list