Slashdot Mirror


Four Root DNS Servers Go IPv6 On February 4th

I Don't Believe in Imaginary Property writes "On February 4th, IANA will add AAAA records for the IPv6 addresses of the four root servers. With this transition, it will finally be possible for two internet hosts to communicate without using IPv4 at all. Certain obsolete software may face compatibility problems due to the change, but those issues are addressed in an ICANN report (pdf)."

13 of 228 comments (clear)

  1. Routers! by arth1 · · Score: 5, Informative

    The main problem isn't obsolete software, but hardware. Changing routers to some that support IPv6 isn't done over night. And even if you do, and get IPv6 assigned, it doesn't help unless your provider also supports IPv6 -- else you might as well be tunelling the old way anyhow.

    Regards,
    --
    *Art

  2. So when will I be able to connect? by AlexMax2742 · · Score: 4, Insightful

    So when will this mean that I can actually use IPv6 for connecting to servers?

    Like, when will I be able to open my browser window, type in an IPv6 address, and connect to...say..google?

    --
    I'm the guy with the unpopular opinion
    1. Re:So when will I be able to connect? by discogravy · · Score: 4, Funny

      if you're browsing by IP now anyway you're doing it wrong.

  3. About time.. by ch-chuck · · Score: 5, Funny

    Great, now we can soon get on with the job of assigning static ip addresses to all our toasters, refrigerators, furnaces, thermostats, tv sets, electric hairdryers, etc.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
    1. Re:About time.. by Denis+Lemire · · Score: 5, Informative

      What is so difficult about adding a default rule to your firewall that blocks all incoming connections to your subnet and then adding rules specifically for the devices and services that do require incoming connections?

      ie) deny ip from any to 2610:78:ad::/48

      With NAT you are eliminating the possibility of incoming connections, with IPv6 you can deny connections all you want but can allow incoming connections where required or desired. Sure you can setup a port forwarding rule to allow a service for a given machine, but what happens when you need the same service to go to more than one host? You know need to accommodate for that by changing the incoming port on your real IP.

      Not to mention all the issues raised by protocols that embed IP's that are not routable within the protocol themselves (take the SIP protocol for example). Work-arounds need to be put in place for many protocols on an individual basis in a NAT'd environment. This is a pain in the ass that would be highly unnecessary in a post IPv4 world.

      If you're so fond of the kludge that is NAT, nobody is stopping you from using NAT with IPv6 in combination with a non-routable unique-local prefix (fc00::/7).

      Dragging your feet on adoption of a superior technology that works for every situation in favor of a broken setup that happens to meet YOUR rather limited requirements is delaying progress for the rest of us. ;)

      Generally speaking the consumer world isn't ready for IPv6 yet anyway (Too many Windows machines with limited IPv6 capabilities)... but I still get annoyed with all the anti-IPv6 commentary by those that have not fully investigated the specifics.

      Just the personal pet peeve that is looking forward to moving behind the network design of choice for the 1980's.

  4. Re:Finally by CastrTroy · · Score: 5, Informative

    They don't do dynamic IP addresses because they don't have enough addresses. They do it for stopping you from running a server on your home computer. Sure you can still run a server, but it's harder to run one when your IP address keeps changing.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  5. Re:Finally by tgd · · Score: 4, Insightful

    No... if that was the case, your IP would change.

    IP changes, in my experience from both Comcast and Verizon FIOS, are so rare that they effectively don't happen. I've never had a change with FIOS from the day the service was fired up, and although I can't recall ever having my previous Comcast one change except when I physically moved, its possible it did once or twice.

    If they want to block servers, they'd block inbound ports.

    Dynamic IP addresses are used because its the only possible way to do it without having techs setting up every joe six pack or grandmothers computer.

  6. Re:two of 'em, eh? by evanbd · · Score: 4, Insightful

    Yeah, when slashdot drops it's IPv4 address, then I'll believe in this IPv6 nonsense.

    OK, admit it... how many of us would go figure out how to run IPv6 if it was required to get a /. fix?

  7. Re:No, wait, not THAT game server... by VGPowerlord · · Score: 4, Funny

    Don't worry, you'll have no trouble remembering the new address. It's b439:88fa:31d3:0507:613a:426c:99ba:02e2 .

    --
    GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  8. Re:Why did they skip 64-bits? by romiz · · Score: 4, Interesting

    I belive that they skipped the 64-bits address to be able to fit the 48-bit MAC (Level 2) address inside the IP (Level 3/4) address, and thus avoiding the need for the router to use ARP to find the MAC address corresponding to a local IP address.

  9. IANAIANA by PixelScuba · · Score: 5, Funny

    I Am Not An Internet Assigned Numbers Authority.

  10. Mixed up acronyms by MarkGriz · · Score: 4, Funny

    Certain obsolete software may face compatibility problems due to the change, but those issues are addressed in an ICANN report Wouldn't that be handled better with an ICANT report?
    --
    Beauty is in the eye of the beerholder.
  11. Re:No, wait, not THAT game server... by teslatug · · Score: 4, Funny

    Indeed, just as easy as the new emergency number