Will this work, is it the best way?

[Lloyd Chang]

Hello Steve,

• Best answer is try and see if it meets your expectations; thanks

• While reading your snippet, my initial questions are — Why 2 servers?
Why not simplify?

• In your proposal: server1, listen to ?? TCP port(s) on public IPv4,
and IPv6 to proxy_pass to server2, then server2 listen on public IPv6, and
IPv4 to proxy_pass to subdomain, with upstream (perhaps for load
balance and/or failover?) — As you agree, this is slightly complicated

• Why not simplify? — Reconfigure DNS for cname-server1 to
server2, for IPv4 and IPv6

• In your snippet, server2 supports IPv4 and IPv6 if you expect it to
upstream via private IPv4 127.0.0.1:[…]

• I don't fully understand why server2 upstream isn't IPv6 ::1:[…]
considering your primary intent for server2 is IPv6 usage

• Perhaps you meant upstream localhost:[…] to try both IPv4 and IPv6? Thanks

Cheers,
Lloyd

On Friday, January 30, 2015, Steve Wilson <lists-nginx at swsystem.co.uk>
wrote:

> Hi,
>
> Slightly complicated setup with 2 nginx servers.
>
> server1 has a public ipv4 address using proxy_pass to server2 over ipv6
> which only has a public ipv6, this then has various upstreams for each
> subdomain.
>
> ipv6 capable browsers connect directly to server2, those with only ipv4
> will connect via server1.
>
> I'm currently considering something like the below config.
>
>
> server1 - proxy all subdomain requests to upstream ipv6 server:
>
> http {
>  server_name *.example.com;
>  location / {
>   proxy_pass http://fe80::1337;
>  }
> }
>
> server2:
>
> http {
>  server_name ~^(?<subdomain>\w+)\.example\.com$;
>  location / {
>   proxy_pass http://$subdomain
>  }
>
>  upstream subdomain1 {
>   server 127.0.0.1:1234;
>  }
> }
>
> The theory here is that each subdomain and upstream would match, meaning
> that when adding another upstream it would just need the upstream{} block
> configuring and automatically work.
>
> I realise there's dns stuff etc but that's out of scope for this list and
> I can deal with that.
>
> Does this seem sound? It's not going to see major usage but hopefully this
> will reduce work when adding new upstreams.
>
> If you've a better way to achieve this please let me know.
>
> Steve.
>
> _______________________________________________
> 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/20150131/0b260ef5/attachment.html>