IPv6 Issues / Question

holstebm nginx-forum at nginx.us
Fri May 13 22:54:06 MSD 2011

Last night I had my provider (Linode) add IPv6 support for my server.  I
also had them assign me an IPv6 pool to use.

I have Nginx 1.0.2 compiled with IPv6 support, restarted my Nginx and
everything was fine all night and most of the morning.  However, within
minutes of me adding AAAA records to my domains, Nginx stopped and
running and took the IPv4 networking down with it.  I hadn't even
restarted Nginx after adding the records.

Upon reboot with Nginx disabled, everything runs fine.  I start Nginx
and make a single IPv4 page request, the network is completely gone
again  on all ports.

I don't believe in coincidences so what could adding AAAA records to
domains Nginx is listening for on port 80 trigger?  Nginx had been
running without problems for 12 hours with IPv6 enabled on the server
with an assigned global scope IPv6 address.  Within minutes of me adding
those AAAA records, the trouble began.

I don't see anything in the logs that helps.  Here is my configuration
for Nginx:

nginx: configure arguments: 
 --add-module=/usr/local/rvm/gems/ruby-1.9.2-p0 at rails3/gems/passenger-3.0.2/ext/nginx
 --with-cc-opt='-pipe -s -O3 -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -mmmx -msse -msse2 -msse3
-mfpmath=sse -mtune=native -march=native -enable-new-dtags -DNODEBUG
-DNDEBUG -enable-stdcall-fixup -frerun-loop-opt -ftracer'

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,197875,197875#msg-197875

More information about the nginx mailing list