Line 178: |
Line 178: |
| | | |
| | | |
− | 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 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: |
| | | |
| | | |
Line 191: |
Line 191: |
| | | |
| | | |
− | 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 resolvers in your DNS search list 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 - if the resolver fails to respond then you may encounter significant delays when attempting to lookup a host. In a linux environment this can be checked using a command similar to: |
| | | |
| machine:/home/user1 # '''host ipv6.chappell-family.com 2001:4860:4860::8888''' | | machine:/home/user1 # '''host ipv6.chappell-family.com 2001:4860:4860::8888''' |
Line 205: |
Line 205: |
| | | |
| | | |
− | Note that it isn't necessary to access your DNS resolver using IPv6 if you don't want to - as long as the DNS server supports AAAA queries then that is sufficient. This is the same query using Google's IPv4 resolver: | + | Note that it isn't necessary to access your DNS resolver using IPv6 if you don't want to - as long as the DNS server supports AAAA queries then this is sufficient. The same query, but on a windows machine, using Google's IPv4 resolver: |
| | | |
− | machine:/home/user1 # '''host ipv6.chappell-family.com 8.8.4.4'''
| |
− |
| |
− | Using domain server:
| |
− | Name: 8.8.4.4
| |
− | Address: 8.8.4.4#53
| |
− | Aliases:
| |
− |
| |
− | ipv6.chappell-family.com has address 212.159.122.74
| |
− | ipv6.chappell-family.com has IPv6 address 2001:470:1f08:185c::2
| |
− | ipv6.chappell-family.com mail is handled by 10 mail.ipv6.chappell-family.com.
| |
| | | |
− | | + | C:\Users\user1>'''nslookup ipv6.chappell-family.com 8.8.4.4''' |
− | The equivalent check on a windows machine would be the following (this time using an Hurricane Electric DNS resolver):
| + | Server: google-public-dns-b.google.com |
− | | + | Address: 8.8.4.4 |
− | C:\Users\user1>'''nslookup ipv6.chappell-family.com 2001:470:20::2''' | |
− | Server: ordns.he.net | |
− | Address: 2001:470:20::2 | |
| | | |
| Non-authoritative answer: | | Non-authoritative answer: |
Line 229: |
Line 216: |
| Addresses: 2001:470:1f08:185c::2 | | Addresses: 2001:470:1f08:185c::2 |
| 212.159.122.74 | | 212.159.122.74 |
− |
| + | |
| | | |
| | | |