Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Thursday May 05 2016, @06:36PM   Printer-friendly
from the not-yet dept.

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? ]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Thursday May 05 2016, @06:47PM

    by Anonymous Coward on Thursday May 05 2016, @06:47PM (#342169)

    Why use DHCPv6 when SLAAC is perfectly capable of offering a DNS configuration?

  • (Score: 2, Informative) by daaelar on Thursday May 05 2016, @06:55PM

    by daaelar (5403) on Thursday May 05 2016, @06:55PM (#342175)

    Because SLAAC would only get you an address on your router, and the idea is to avoid NAT. DHCPv6 has the concept of Prefix Delegation. When you send a DHCPv6 Solicit message from a typical home gateway, you're requesting an IA_NA (Non-temporary address, which goes on the WAN port) and an IA_PD (Prefix Delegation: this goes on your whole LAN as typically a /64) so each of your connected devices has a routable address.

    • (Score: 0) by Anonymous Coward on Thursday May 05 2016, @07:04PM

      by Anonymous Coward on Thursday May 05 2016, @07:04PM (#342181)

      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.

      • (Score: 0) by Anonymous Coward on Friday May 06 2016, @04:00PM

        by Anonymous Coward on Friday May 06 2016, @04:00PM (#342584)

        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.