Changes

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:

   host ipv6.chappell-family.com 2001:4860:4860::8888

   machine:/home/user1 # '''host ipv6.chappell-family.com 2001:4860:4860::8888'''

    

    

   Using domain server:

   Using domain server:

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 that is sufficient. This is the same query using Google's IPv4 resolver:

   host ipv6.chappell-family.com 8.8.4.4

   machine:/home/user1 # '''host ipv6.chappell-family.com 8.8.4.4'''

      

      

   Using domain server:

   Using domain server:

   nslookup ipv6.chappell-family.com

   '''nslookup ipv6.chappell-family.com'''