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 Hyperturtle on Friday May 06 2016, @01:01AM
Yes, even being an IPV6 half-ass can yield you some good gigs. Being able to identify this in front of the businesses with money can make you a hero, even if you make gobs of money, you still can save them gobs by getting rid of those people that just are riding the crest, like those self identified experts that called themselves cloud engineers. I havent heard a cringe worthy name for IPV6 specific engineers, but I think someone is trying to invent one, somewhere...
The fact that it costs so much to go legit with IPV6 (and get your own ranges) has rendered the field as a place filled with half-asses, so get going while the going is good. It is hard to use IPV6 locally with most consumer stuff right now as it is. Much of it is rudimentary and basic, but yeah it sorta works. IPV4 on NT 4.0 works better in comparison to IPV6 on most stuff one can get from the local best buy or similar store (this has been my experience). IPV6 may work better on custom firmwares on that same best buy hardware -- but perhaps only a few reading this will go out of their way to do that. And find their ISP has a real problem with it.
I expect 2017/2018 to be when things really pick up speed -- because of IoT and smart this and smart that, and robot cars and etc... don't expect them all to use carrier grade NAT!