Line 1: |
Line 1: |
| == IPv6 DEBUG == | | == IPv6 DEBUG == |
| | | |
− | Debug suggestions related to IPv6 configuration issues that might be encountered when accessing my [http://ipv6.chappell-family.com/ipv6tcptest/ IPv6 firewall tester.] | + | Debug suggestions related to IPv6 configuration issues that might be encountered when accessing the [https://ipv6.chappell-family.com/ipv6tcptest/ IPscan IPv6 firewall tester.] |
| | | |
| For general IPv6 debug please see: | | For general IPv6 debug please see: |
Line 12: |
Line 12: |
| | | |
| === General IPv6 Connectivity === | | === 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: |
| | | |
Line 183: |
Line 184: |
| | | |
| | | |
− | Based on the fact that must have already accessed my server using IPv4, in order to be reading this, then the following IPv4 A-record lookup should work: | + | Based on the fact that must have already accessed the IPscan domain using IPv4, in order to be reading this, then the following IPv4 A-record lookup should work: |
| | | |
| | | |
Line 194: |
Line 195: |
| Non-authoritative answer: | | Non-authoritative answer: |
| Name: ipv6.chappell-family.com | | Name: ipv6.chappell-family.com |
− | Address: 212.159.122.74 | + | Address: B.C.D.E |
| | | |
| | | |
Line 202: |
Line 203: |
| === DNS Resolver Issues === | | === 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: |
| | | |
| | | |
− | * [http://www.sixxs.net/tools/dnscache/ SixXS DNS Servers]
| |
| * Hurricane Electric - see Available DNS resolvers section of your tunnel setup (may be 2001:470:20::2 and 74.82.42.42) | | * Hurricane Electric - see Available DNS resolvers section of your tunnel setup (may be 2001:470:20::2 and 74.82.42.42) |
| | | |
Line 212: |
Line 212: |
| | | |
| * [https://developers.google.com/speed/public-dns/docs/using Google DNS Servers] | | * [https://developers.google.com/speed/public-dns/docs/using Google DNS Servers] |
− | * [http://www.opendns.com/technology/ipv6/ OpenDNS IPv6 trial] | + | * [https://support.opendns.com/hc/en-us/articles/227986667-Does-OpenDNS-Support-IPv6- OpenDNS IPv6] |
| | | |
| | | |
Line 306: |
Line 306: |
| | | |
| * [http://ipv6.google.com Google's IPv6-only-URL] | | * [http://ipv6.google.com Google's IPv6-only-URL] |
− | * [http://pi.ipv6.chappell-family.co.uk/ An IPv6-only-URL] | + | * [http://www6.chappell-family.co.uk/ An IPv6-only-URL] |
| | | |
| | | |
Line 323: |
Line 323: |
| | | |
| Accept the warning about dragons, and then in the filter bar enter: | | Accept the warning about dragons, and then in the filter bar enter: |
− |
| |
| | | |
| ipv6 | | ipv6 |
Line 329: |
Line 328: |
| | | |
| The resulting list should now show an entry: | | The resulting list should now show an entry: |
− |
| |
| | | |
| network.dns.disableIPv6 | | network.dns.disableIPv6 |
Line 335: |
Line 333: |
| | | |
| If this entry is set to '''true''' then double click on the entry to change its sense to '''FALSE'''. Then try again! | | If this entry is set to '''true''' then double click on the entry to change its sense to '''FALSE'''. Then try again! |
− |
| |
| | | |
| | | |
| === IPv6-only URL Test === | | === IPv6-only URL Test === |
| | | |
− | and finally pointing your web browser towards my [http://pi.ipv6.chappell-family.co.uk/ IPv6-only Raspberry Pi Powered port scanner] should also work. | + | and finally pointing your web browser towards the [http://www64.chappell-family.co.uk/cgi-bin6/ipscanjs.cgi IPv6-only Raspberry Pi Powered port scanner] should also work. |
− | | |
− | | |
| | | |
− | This website publishes a Privacy Policy. Continued use of this website implies your consent to the use of data outlined in the policy.
| |
| | | |
| | | |
− | ----
| + | This website publishes a Privacy Policy (link at the bottom of every page). Continued use of this website implies your consent to the use of data outlined in the policy. |