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)."

23 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

    1. Re:Routers! by palegray.net · · Score: 3, Insightful

      I ask this because I honestly don't know. How many routers on the net are embedded devices capable of receiving firmware updates to cope with the additional functionality? Or, how many full-fledged "router in a box" style server systems are capable of receiving software updates, or already support IPV6?

    2. Re:Routers! by ArsonSmith · · Score: 3, Informative

      This may beg for the question, but it does not beg the question.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    3. Re:Routers! by Anonymous Coward · · Score: 3, Insightful

      Part of the problem is that, even though most routers can get software updates in the field, older models only have hardware accelerated IPv4 support. If you upgrade these routers to IPv6, they have to do everything with their puny CPU, which means the same router can handle fewer IPv6 packets than IPv4 packets.

  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.

    2. Re:So when will I be able to connect? by Chris+Mattern · · Score: 3, Informative

      Right now.

      No, really.


      You appear to have misspelled your answer: the correct answer is "Real soon now. Not really."

      Google has no IPv6 address to connect to. Nor have most other major net sites. IPv4 is still the only way to connect to almost all of the internet.

      Chris Mattern
  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.

    2. Re:About time.. by growse · · Score: 3, Informative

      Everyone, lets all hold hands and repeat now:

      Firewalling and NAT are different things...
      Firewalling and NAT are different things...
      Firewalling and NAT are different things...

      --
      There is nothing interesting going on at my blog
  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. Best IPv6 Read ever (not the article) by Anonymous Coward · · Score: 3, Informative
    But the off topic link I'm making to the wikipedia page...

    IPv6

    common to see examples that attempt to show that the IPv6 address space is absurdly large. For example, IPv6 supports 2128 (about 3.4×1038) addresses, or approximately 5×1028 addresses for each of the roughly 6.5 billion people[1] alive today. In a different perspective, this is 252 addresses for every star in the known universe [1] - a million times as many addresses per star than IPv4 supported for our single planet. These examples, however, have an underlying and inco
  6. 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.

  7. No, wait, not THAT game server... by jackpot777 · · Score: 3, Funny

    I'm just hoping the Enemy Territory server I play on doesn't move too quickly to the switch to IPv6. It took me ages to load their map rotation, but it's a good selection and their bots are a nice challenge. It has taken me months already to remember the 216.27.112... wait, is it 112.48, or 48.112 at the end? And that 27 doesn't look right. It ends in :27962, I know that. Or is it :27964?

    Ah crap, I forgot the number again.

    Damn you, progress.

    --
    Shiny. Let's be bad guys...
    1. 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
    2. Re:No, wait, not THAT game server... by teslatug · · Score: 4, Funny

      Indeed, just as easy as the new emergency number

  8. Re:two of 'em, eh? by shentino · · Score: 3, Informative

    Actually, v4 and v6 are quite independent. A single host can have BOTH at the same time.

    I'd hope /. keeps its v4's at least until my college switches to v6.

    I think it's backward compatibility IIRC.

  9. 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?

  10. 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.

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

    I Am Not An Internet Assigned Numbers Authority.

  12. 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.
  13. Re:Finally by raju1kabir · · Score: 3, Insightful

    I think many of us geeks know that you can also use methods like DHCP to configure static IPs. What you are benefiting from here is DHCP, not your dynamic IP.

    --
    "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
  14. Re:Human readability by gbjbaanb · · Score: 3, Insightful

    IP addresses:
    I can't remember my IPv4 addresses without looking them up, so I'd be no worse off than with IPv6. You'll get older too son, then you'll agree with me :)

    As for web hosting providers, they won;t ever have to 'change your IP address', they'll just have to tell you it in the first place, then you're done.

    In both cases, IPv6 supports auto-registration so you won't have to fiddle with it anyway. As the IETF says "Since IPv6 addresses are too long to remember and EUI64-based addresses are too complicated to remember, they are not suitable for such identifiers"

    IIRC you don't need DHCP anymore with stateless autoconfiguration.

    NAT:
    think for a moment what NAT does. All you have is your router attached to the internet, and all your computers connected to the router. Unless you explicitly allow incoming connections to pass through, your PCs are "firewalled" at the router.

    If you have IPv6, you'll still have the router. I hope that all router manufacturers will be shipping them with incoming connectivity disabled by default, just like it is at the moment. Then, you'll be no less secure with IPv6 than you are today.

    You will have the benefit of being able to "DMZ" as many of your PCs as you like, not just one of them. This is best of both worlds.

    I think IPv6 will be a good thing, if it ever happens. I can't see that happening anytime soon though, there's too much infrastructure out there.