An Anonymous Coward writes:
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.
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? ]
There are worse things. I'm on Suddenlink and their DNS resolves pretty much everything to a Suddenlink IP and attempts https hijack. They want you to install their wildcard cert to make it possible. So I'm using the Google DNS servers until they get around to shutting that down, then it will be time to pay extra for VPN service.
I used to run an open DNS server for people in circumstances such as yours. Then one day I noticed that the entire 100Mb/s was in use. Turns out some criminals were using DNS reflection attacks against someone else using my server, so that had to stop. As it turned out, a low-power Celeron can't handle processing iptables flood rules with the volume of traffic the crooks were sending, so bye bye public DNS server.
It was much the same story with NTP.
yeah, or you could use dnsmasq and dnscrypt-proxy and use the default nameserver or pick another.