Welcome! Log In Create A New Profile

Advanced

Feature proposal: use names instead of IPv6 addresses

Ivan Vilata i Balaguer
January 13, 2010 05:48AM
Hi all,

I'm doing some experiments with IPv6 and I've seen that the following statement
in an nginx ``server`` block::

listen www.example.com:80;

Binds nginx to www.example.com's IPv4 address, but not to its IPv6 address if
it has one (e.g. the name has an ``AAAA`` entry in DNS). I'm, however, able to
specify the IPv6 address directly::

listen [1111:2222:3333::1]:80;

But using the name inside the brackets yields an "invalid IPv6 address" error::

listen [www.example.com]:80;

So, wouldn't it be nicer if nginx supported this syntax? Or maybe I'm missing
something?

Another possibility would be for nginx to automatically bind to both IPv4 and
IPv6 addresses associated to the name given in the ``listen`` directive, but I
guess this should need more elaboration and some use cases.

Thanks,

::

Ivan Vilata i Balaguer -- http://ivan.lovesgazpacho.net/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

Feature proposal: use names instead of IPv6 addresses

Ivan Vilata i Balaguer January 13, 2010 05:48AM

Re: Feature proposal: use names instead of IPv6 addresses

Piotr Sikora January 13, 2010 12:54PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 147
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready