579
edits
Changes
Jump to navigation
Jump to search
Line 8:
Line 8: + Line 69:
Line 70: + Line 191:
Line 193: + Line 232:
Line 235: + Line 280:
Line 284: − + Line 326:
Line 330: + +
no edit summary
=== General IPv6 Connectivity ===
First check your general IPv6 connectivity. At a command prompt or terminal check that your machine has a global unicast IPv6 address allocated (i.e. 2000::/3, so begins either 2XXX or 3XXX) as shown in these examples:
First check your general IPv6 connectivity. At a command prompt or terminal check that your machine has a global unicast IPv6 address allocated (i.e. 2000::/3, so begins either 2XXX or 3XXX) as shown in these examples:
If this is NOT successful then either your DNS AAAA lookups or general IPv6 connectivity is broken (determine which based on your error messages).
If this is NOT successful then either your DNS AAAA lookups or general IPv6 connectivity is broken (determine which based on your error messages).
=== DNS Related Issues ===
If you have a name lookup error then it is possible to bypass the DNS lookups and ping google's IPv6 host directly:
If you have a name lookup error then it is possible to bypass the DNS lookups and ping google's IPv6 host directly:
If you don't get a similar response then you need to investigate your DNS setup, or perhaps your ISP's.
If you don't get a similar response then you need to investigate your DNS setup, or perhaps your ISP's.
=== DNS Resolver Issues ===
Some DNS services don't seem to reliably resolve AAAA lookups. In particular, some appear to resolve A and AAAA records with different delays, and/or reliability, which sometimes causes web browsers to determine that only an IPv4 address exists since the IPv6 lookup resolves too slowly/unreliably. You can try one of the publicly accessible DNS resolvers as an alternative to your current providers' if you believe that this might be the case. For those using a tunneled IPv6 connection then it is likely that your tunnel provider also offers a DNS resolver:
Some DNS services don't seem to reliably resolve AAAA lookups. In particular, some appear to resolve A and AAAA records with different delays, and/or reliability, which sometimes causes web browsers to determine that only an IPv4 address exists since the IPv6 lookup resolves too slowly/unreliably. You can try one of the publicly accessible DNS resolvers as an alternative to your current providers' if you believe that this might be the case. For those using a tunneled IPv6 connection then it is likely that your tunnel provider also offers a DNS resolver:
=== Browser IPv6 Prioritisation ===
If all of the above was successful then your browser may not be prioritising IPv6 DNS requests. The following browsers are known to support IPv6 prioritisation:
If all of the above was successful then your browser may not be prioritising IPv6 DNS requests. The following browsers are known to support IPv6 prioritisation:
== WINDOWS 7 RESPONSES ==
=== WINDOWS 7 RESPONSES ===
A correctly configured Windows 7 machine shows the following responses:
A correctly configured Windows 7 machine shows the following responses:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Minimum = 0ms, Maximum = 0ms, Average = 0ms
=== IPv6-only URL Test ===
and finally pointing your web browser towards my [http://www6.ipv6.chappell-family.com/ipv6tcptest/ IPv6-only port scanner] should also work.
and finally pointing your web browser towards my [http://www6.ipv6.chappell-family.com/ipv6tcptest/ IPv6-only port scanner] should also work.