[141994] in North American Network Operators' Group
Re: AAAA on various websites, but they all forgot to enable them
daemon@ATHENA.MIT.EDU (Jeroen van Aart)
Wed Jun 15 15:14:26 2011
Date: Wed, 15 Jun 2011 12:14:15 -0700
From: Jeroen van Aart <jeroen@mompl.net>
To: NANOG list <nanog@nanog.org>
In-Reply-To: <op.vwrx4ax54oyyg1@alvarezp-ws>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Octavio Alvarez wrote:
> In fact. Although a website of mine worked flawlessly in a dual-stack
> but it did NOT in an IPv6-only environment. Unfortunately, the problem
> has to be fixed in the DNS provider, which though supporting AAAA
> records was enough to "support IPv6".
Why not run your own nameserver if it is your website assuming you own
the domain?
Out of curiosity, what are the options you need to use to properly
enable bind for IPv6? To me it appears there isn't that much to it, it
almost works out of the box with 1 or 2 things turned on. Then you just
add the appropriate zone files or records. Am I missing something
blatantly obvious that will break it?
> dig -6 +trace is our friend here.
How would you apply this command to determine correct IPv6 resolving?
Thanks,
Jeroen
--
http://goldmark.org/jeff/stupid-disclaimers/
http://linuxmafia.com/~rick/faq/plural-of-virus.html
