• Wilzax@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    11 months ago

    Why do I care what ICANN says I can do on my own network? It’s my network, I do what I want.

      • Wilzax@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        11 months ago

        Well as long as the TLD isn’t used by anyone it should work internally regardless of what ICANN says, especially if I add it to etc/hosts

        • Magiilaro@feddit.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          German router and network products company AVM learned the hard way that this is a bad idea. They use fritz.box for their router interface page and it was great until tld .box became publicly available and somebody registered fritz.box.

          Having a reserved local/internal only tld is really great to prevent such issues.

        • friend_of_satan@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          Sure, you can do whatever you want. You could even use non-rfc1918 addresses and nobody can stop you. It’s just not always a great idea for your own network’s functionality and security. You can use an unregistered TLD if you want, but it’s worth knowing that when people and companies did that in the past, and the TLD was later registered, things didn’t turn out well for them. You wouldn’t expect .foo to be a TLD, right? And it wasn’t, until it was.

    • Melllvar@startrek.website
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      The value of the DNS is that we all use the same one. You can declare independence, but you’d lose out on that value.