01-20-2011, 10:58 PM
|
|
|
Confirmed User
Industry Role:
Join Date: Jan 2003
Location: In a Tater Patch
Posts: 2,321
|
Quote:
Originally Posted by Ron Bennett
No need to rush getting an IPv6 IP, since there's, practically speaking, an unlimited supply of them. Get them as needed.
Running both IPv4 and IPv6 right away would seem the prudent thing to do, but it comes with a tradeoff of loss of visitors. While IPv4 and IPv6 are similar in name, they are technically very different; not backwards compatible...
And so if a visitor has some IPv6 connectivity (ie. their OS and/or ISP), but their router and/or something along the line doesn't do IPv6 correctly, instead of falling-back to IPv4 (as one would reasonably expect), the visitor will likely get a very long pause (many will click-off thinking the page is broken) and/or get a site not found error.
In short, if running IPv4 / IPv6, expect at least a 10%+, and potentially far more, drop in visitors. For more info, read the various news articles regarding the tough challenges / tradeoffs Yahoo and Google are confronting as they work to transition over to IPv6.
Ron
|
I'm sorry but you either support IPv6 and AAAA records which DNS would utilize/pickup or you wouldn't. There is no pause/stop/start falling back to IPv4. You either support IPv6 and AAAA or you don't. Please show me some proof that this happens. You might be thinking of someone doing some sort of failed IPv6 to IPv4 tunneling or NATing which is not native IPv6. I have never seen someone "automatically" fall back to IPv4 if they are using IPv6 natively. You would be rather shocked to see DNS queries request AAAA records for your zones if you paid attention to it. |
|
|