579
edits
Changes
Jump to navigation
Jump to search
Line 179:
Line 179: + − + + + +
no edit summary
Some DNS services don't seem to reliably resolve AAAA lookups. In particular, some appear to resolve A and AAAA records with variable delays which sometimes causes web browsers to determine that only an IPv4 address exists since the IPv6 lookup resolves too slowly. 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 variable delays which sometimes causes web browsers to determine that only an IPv4 address exists since the IPv6 lookup resolves too slowly. 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]
* [http://www.sixxs.net/tools/dnscache/ SixXS DNS Servers]
* Hurricane Electric - see Available DNS resolvers section of your tunnel setup
* Hurricane Electric - see Available DNS resolvers section of your tunnel setup (may be 2001:470:20::2 and 74.82.42.42)
Other public IPv6 DNS resolvers:
Other public IPv6 DNS resolvers:
* [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]
* [http://www.opendns.com/technology/ipv6/ OpenDNS IPv6 trial]
The order in which you list the DNS resolvers is important - so when trying a new resolver ensure that you place it at the front of your resolver list. Note that it is worth checking that you can communicate with the resolver before modifying your resolver list since you may otherwise encounter significant delays when attempting to lookup a host. In a linux environment this can be checked using a command similar to:
The order in which you list the DNS resolvers is important - so when trying a new resolver ensure that you place it at the front of your resolver list. Note that it is worth checking that you can communicate with the resolver before modifying your resolver list since you may otherwise encounter significant delays when attempting to lookup a host. In a linux environment this can be checked using a command similar to: