Configuring a subnet in an upstream server

[Dynastic Space]

I used a poor example.
The functionality I was interested in was adding a range of application
servers, all part of the same domain.

D

On Mon, Apr 3, 2017 at 11:04 AM, B.R. via nginx <nginx at nginx.org> wrote:

> What would be the meaning of that?
>
> How do you route traffic to 192.168.0.0? Do you really want to send
> requests to 192.168.255.255?
> How would you handle requests sent to some servers (but not all) if some
> are not responsive?
>
> I suspect what you want to use is dynamic IP addresses for your backends.
> Good news: you can use domain names.​
> ---
> *B. R.*
>
> On Sun, Apr 2, 2017 at 8:42 AM, Dynastic Space <dynasticspace at gmail.com>
> wrote:
>
>> Is it possible to configure a collection of servers using subnet notation
>> in the upstream server knob? e.g. server 192.168.0.0/16.
>>
>> Thanks,
>>
>> Dynastic
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
> _______________________________________________
> 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/20170403/e910a698/attachment.html>