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
  • blackstrat@lemmy.fwgx.ukEnglish
    4·
    6 months 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.

    • NaN@lemmy.sdf.orgEnglish
      3·
      6 months 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.

    • Encrypt-Keeper@lemmy.worldEnglish
      2·
      6 months ago

      People have been told for a very long time not to use fake TLDs. I don’t think it’s reasonable to accommodate people who can’t follow instructions.

    • fishpen0@lemmy.worldEnglish
      1·
      6 months ago

      Seconding the other comment, lots of orgs picked .lan and then over the last few years have moved things into the cloud and .lan has become a meaningless soup since half the shit isn’t even on local network. Now it just means “needs a vpn or ztn to talk to”

      Luckily my last three orgs finally bought a second domain for private dns. It’s quickly becoming a pattern that myorg.com owns myorg.tech or whatever for private traffic. Domains are cheap as fuck compared to everything else a business spends money on, it’s really silly how many people are using hacks for this

  • Snot Flickerman@lemmy.blahaj.zoneEnglish
    2·
    6 months 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, anyone taking bets on how many “Internal” TLDs are gonna be used for porn?

    • Robert7301201@slrpnk.netEnglish
      1·
      6 months 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.

  • Decronym@lemmy.decronym.xyzBEnglish
    1·
    6 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    CA (SSL) Certificate Authority
    DNS Domain Name Service/System
    IP Internet Protocol
    SSL Secure Sockets Layer, for transparent encryption
    VPN Virtual Private Network

    5 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

    [Thread #477 for this sub, first seen 2nd Feb 2024, 16:35] [FAQ] [Full list] [Contact] [Source code]

  • deadcatbounce@reddthat.comEnglish
    1·
    6 months 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 corresponds to.

    What am I missing?

    Update: I’m not sure I formed my question correctly because I’m none the wiser. That’s my fault, I think.

  • Corngood@lemmy.mlEnglish
    0·
    6 months 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 🤮

    • perishthethought@lemm.eeEnglish
      0·
      6 months 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.