APNIC reminds us that "there are now a large number of ISPs, data centres, cloud services, and software that now support IPv6" and "enabling IPv6 can be as simple as clicking a button on your WiFi router."
I turned it on, with Comcast I received an IPv6 route but no DNS server. Fortunately, Google Public DNS has unmemorable addresses, which I was able to configure manually.
2001:4860:4860::8888
2001:4860:4860::8844
It works. "There's only one thing left for you to do: Turn it on!"
[ ed: What are the alternatives to Google's Public DNS? ]
(Score: 2) by archfeld on Friday May 06 2016, @02:10AM
DNS on Time Warner Cable here in Yuma doesn't support IPV6 either. My local hardware does but I had to move to OpenDNS. TWC had their DNS configured to sequential IPs on the same subnet anyways, so anytime there was any sort of issue, both DNS suffered from the same problem. Anyone know if there is any noticeable difference between OpenDNS or GoogleDNS ?
For the NSA : Explosives, guns, assassination, conspiracy, primers, detonators, initiators, main charge, nuclear charge
(Score: 0) by Anonymous Coward on Friday May 06 2016, @05:36AM
Which is fine. Because they are dual stack. You can get AAAA records from the ipv4 DNS servers.
> google.com
Server: dns-cac-lb-01.rr.com
Address: 209.18.47.61
Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4002:c07::8b
74.125.21.138
74.125.21.101
74.125.21.139
74.125.21.102
74.125.21.100
74.125.21.113
-----
ping google.com
Pinging google.com [2607:f8b0:4002:c08::8b] with 32 bytes of data:
Reply from 2607:f8b0:4002:c08::8b: time=28ms
Reply from 2607:f8b0:4002:c08::8b: time=33ms
Reply from 2607:f8b0:4002:c08::8b: time=39ms
Reply from 2607:f8b0:4002:c08::8b: time=33ms
Ping statistics for 2607:f8b0:4002:c08::8b:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 39ms, Average = 33ms