315
It's easier to remember the IPs of good DNSes, too. (lemmy.sdf.org)
submitted 2 years ago* by to c/programmer_humor@programming.dev
186 comments fedilink hide all child comments
 

Today in our newest take on "older technology is better": why NAT rules!

you are viewing a single comment's thread
view the rest of the comments
[–] 34 points 2 years ago (2 children)

Ha I can remember the ipv6 of cloudflare DNS just fine! It's uh..... something : something : something :: 1111

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 13 points 2 years ago* (last edited 2 years ago) (1 child)

    2606:4700:4700::1111

    Hmm, maybe Google is easier:
    2001:4860:4860::8888

    Quad9 is 2620:fe::fe or 2620:fe::9

    I don't understand why they can't get better addresses than that. Like surely 1::1 would be valid?

    Edit: So IANA only control addresses 2001:: and up and there are quite a few IETF reservations within that. I don't know why they picked such a high number to start at. Everything else seems IETF reserved with a little space allocated for special purposes (link-local, multicast, etc.).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (3 children)

    Address space is so huge that iirc the only global addresses in use are 2xxx::

    Its so huge that it's not needed to use anything else is the goal as far as I see. If it starts with 2, it's global.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Also for routing table reasons. Ipv6 needs to use prefixes to do link aggregation or it just gets too bjg

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    I can see that, but surely there wouldn't be much difference matching the first 4bits (0x2XXX, 0xfXXX) vs the first 16 (0x0001)?
    0:: is presumably all for loopback-type stuff, but I don't see a reason not to use 1:: through 1fff:: and they would be much easier to type/remember/validate for public DNS servers which are needed before name resolution is available.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    IPv6 is big enough to give 10 billion unique addresses for every grain of sand on earth and still have some left over. Just in case we need to, I guess.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    It's great that the address space is so large. When designing a new system, you want to make sure it'll hopefully never encounter the same issue as the old system, to ensure you don't have to migrate yet again.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    Sure. But the IPv6 implementation is a bit like if we went "you know the y2038 problem of 32 bit numbers, and how goin under 1970 is sometimes hard? Lets solve it by making it start from the big bang and store time as a 256 bit integer so we don't run out until year 3.1 x 10^69".

    IPv6 is big enough for 340,282,366,920,938,463,463,374,607,431,768,211,456 unique addresses. Are we expecting to create an universe consuming army of exponentially replicating paper clip converting robots that each need an IPv6 address or something?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    Having a large range has a number of benefits though. Companies that have dozens of IPv4 ranges may be fine with a single IPv6 range, which simplifies routing rules.

    A lot of features in IPv6 take advantage of the fact that networks have at least a /64 range (at least if they're built correctly according to RFC4291 and newer specs). SLAAC is a major one: Devices can auto-configure IP addresses without having to use something like a stateful DHCP server.

  • permalink
  • fedilink
  • source
  • parent