The plan is to keep the world at bay by never recording it in the DNS root – like many already do with a subdomain for an intranet
  • @[email protected]English
    13•1 year ago

    If we didn’t have a bazillion TLDs these days we’d be ok and everyone can carry on using .local or .lan and be happy that they’re not real TLDs. Now when anything could be a TLD because every word you’ve ever heard is a TLD, you don’t know if its real or not.

    • NaNEnglish
      4•1 year ago

      Reserved TLDs are documented. The issue is they prioritized all the crazy ones before they added what people at home and businesses were actually using. ICANN won’t sell .lan because it is used too much. They haven’t tried so there is no official decision, but they won’t - they did try .corp and .home and abandoned it.

      .local is reserved in RFC 6762, but for multicast DNS.

        • NaNEnglish
          1•1 year ago

          The special use list for use by individuals and business is actually very small and hasn’t been updated in a long time, which is a big part of the problem with people inventing their own.

  • Snot FlickermanEnglish
    10•1 year ago

    Looks like *.lair is still a great one for a local TLD.

    Just rock your “Evil.subterranean.lair” people.

    You could also go for “Wicked.volcano.lair”

    Or even “morallywrong.commercialrealestate.lair”

    Also, bets on how many “Internal” TLDs are gonna be used for porn?

    • @[email protected]English
      6•1 year ago

      Very few as this ruling would reserve .internal for local DNS only and forbid it at the global level. This is ICANN’s solution to people picking random .lan .local .internal for internal uses. You’ll be able to safely use .internal and it will never resolve to an address outside your network.

  • @[email protected]English
    10•1 year ago

    Huh, I’ve seen .local used for this quite a bit and only just now realised that it’s meant for something else.

    I’ve also seen .corp 🤮

    • @[email protected]English
      9•1 year ago

      And .home.

      Hopefully this .Internal domain takes off and becomes generally recognized as the only correct non-routable domain we all use. Otherwise it’s just the latest addition to the list of possible TLDs and confusion continues.

      • NaNEnglish
        1•1 year ago

        It’s such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They’re safe by ICANN policy, but unsanctioned.

        .home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I’ve used . internal for lab testing stuff for ages, so this is extra good news for me I guess.

        Really I wish they’d have just reserved the most common ones rather than getting caught in some bureaucratic black hole.

  • deadcatbounceEnglish
    1•1 year ago

    Don’t follow. Help me out someone please.

    The net runs on numbers. The numbers have to be translated into/from the DNS name to the numbers.

    Nominating a DNS name as internal is doesn’t change the fact that we still have to, at some stage, find the (local) network mask that that it corresponds to.

    What am I missing?

    • @[email protected]English
      7•1 year ago

      It’s for internal resources. You can really use whatever subdomain you want internally, but this decision would be to basically say to registrars, this TLD is reserved, we will never sell this TLD to anyone to use. That way you know that if you use it internally, there’s no way a whoopsie would happen where your DNS server finds a public record for this TLD.