Quote - The problem with the IPv6 theory is that it would surely affect a lot more than one site for Internet power users....

It will affect everything on the affected server based on how the DNS tables update, and if it works on the servers it is pointing too. If a server gets dropped from your DNS list, you can't find it with a browser. If it has an IPv6 address, but that doesn't work, it will time out long before it even tries the IPv4 address.

Like I said earlier, I can get on the site, have been able to the whole time. My internet connection uses both IPv4 and IPv6

The nightmere has only just gotten started with IPv6.

Here are some quotes from a recent article about all the problems that are occuring even thou people have not seen much of it, yet.

"On networks that need to support anything other than a Windows Vista/7 monoculture, it's infeasible to turn off stateless autoconfig, because then some systems simply wouldn't get an IPv6 address. Worse, the information that stateless autoconfig is not in use must be multicast by routers. Just one rogue router that says otherwise can make all hosts create those unpredictable temporary addresses.... "

Another problem...

"If something goes wrong with IPv6, nine out of ten times, nobody even notices: most communication is over IPv4 anyway. And if a session is initiated over IPv6 but then fails, it's usually retried over IPv4 automatically. This may happen after a significant delay, or within a fraction of a second. If users complain, it's not unheard of that IPv6 issues get very low priority. For instance, Mac OS X 10.6 Snow Leopard has a serious bug in its DNS code that makes it ignore IPv6 in the DNS when there is a CNAME record involved, a case which is not uncommon. One year and four point updates later, the bug is still there."

Problem gets worse, because what they said no one would notice, is getting noticed. Servers that use IPv6 and pipelining will see problems with the ipv6 router refusing to allow the TCP session to stay open as well.

Another quote:

"An example of the "can't get there from here" problem is the issue with hosts that think they have IPv6, but in reality it doesn't work. Even though we know how to run IPv4 and we know how to run IPv6, we find ourselves in a world where both protocols exist side-by-side, and interact in unexpected ways. Hosts that think they have IPv6 connectivity will try to connect to servers that have an IPv6 address in the DNS over IPv6. But if the IPv6 connectivity then doesn't work, nothing happens for a while until the application times out"

Which equates to "page not found" in a browser.

---

Some things are easy to explain, other things are not........ <- Store ->   <-Freebies->