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? ]
My Verizon router uses ICMPv6 to advertise a /64 prefix and a DNS server. Devices on my LAN take the prefix, pick addresses for themselves, and use the DNS server. There is no NAT.
I believe the parent meant that you're router could use DHCPv6 to get your LAN prefix from your ISP. Your local machines would use SLAAC to get their info from the router. That is, if the router uses SLAAC, it just gets an IP address and not the prefix it needs to broadcast to the LAN. It could then NAT the LAN through its IP, but the local LAN wouldn't have public addresses.