vivek said:
AAAA does works with VB, but IPv6 is not that common. We manager couple of larger customer websites (millions plus hit per day) and only 30-40 Ipv6 unique a day. It is not worth a trouble.
I'm going to disagree with everything you just said. Head's up.
If you actually read the thread that I posted from vbulletin.com you'd know that vBulletin does not completely support IPv6. They use a 15-byte field to store an IP address in presentation format. IPv6 addresses don't always fit in 15 bytes when in presentation form. This means that features tied to IP addresses in vBulletin do not work with IPv6.
Not that common? Says who? Everyone who owns an Airport Extreme wireless gateway and everyone using Windows Vista is connected to the IPv6 internet right now. Throw in all of the nerds (like myself and SirDice from this thread) and you've got an awful lot of IPv6 clients looking for IPv6 content.
I run a vBulletin forum with "only" 100s of thousands of hits a day and yet I see a handful of IPv6 addresses each day.
I can't seem to find reference to it right now but I believe that one of the major consumer ISPs in India is even offering native IPv6 right now.
And trouble? What trouble? How is it any different from IPv4? Put an address on an interface. Add a default route. Update DNS. done. Regardless, even if it were "trouble" to configure I do think its worth it. I want to see the rest of the Internet get off their lazy asses and configure IPv6 so we can quit lolly-gagging around with NAT and, worse, Carrier Grade NAT. I hate to throw The Google into the ring but even Google said it was easy; not exactly the smallest web property on the Internet.
Notice that most other FreeBSD.org properties are v6 enabled. www. mailing lists. FreeBSD as an OS is IPv6 certified. Why wouldn't FreeBSD.org want to make forums.freebsd.org IPv6 enabled?
