• r00ty
    link
    fedilink
    1159 months ago

    Sorry. I chose .local and I’m sticking to it.

    • xcjs
      link
      fedilink
      English
      309 months ago

      I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I’m certainly not going to switch to .internal unless another conflict surfaces.

      I’ve also developed a host-monitoring solution that uses mDNS, so I’m not about to break my own software. 😅

        • xcjs
          link
          fedilink
          English
          109 months ago

          Yeah, that’s why I started using .lan.

      • r00ty
        link
        fedilink
        39 months ago

        Yeah, I don’t really have a use at home for mDNS. None that I can think of, anyway. Pretty sure I was using it before MDNS was a thing.

          • r00ty
            link
            fedilink
            29 months ago

            Oh. Internal hosts, I just setup on my own DNS… No need for that. Printer, can’t say I’ve ever had a problem.

      • anytimesoon
        link
        fedilink
        English
        79 months ago

        I’m using .home and have not had any issues. Would you mind sharing what problems you’ve come across so I know what to expect?

        • @ayyy@sh.itjust.works
          link
          fedilink
          English
          39 months ago

          The main problem I have is waking up in the middle of the night worrying that ICANN pulled some more stupid corrupt bullshit that only makes networking worse and breaks my config.

          Just look elsewhere in this thread: someone thinks that using .honk as a joke is safe. But what about .horse? .baby? .barefoot? .cool? (I stopped scrolling through the list at this point but you can see how arbitrary and idiotic things have become.)

    • @dhtseany@lemmy.ml
      link
      fedilink
      English
      169 months ago

      I still haven’t heard a convincing argument to not use .local and I see no reason to stop.

      • @SirEDCaLot@lemmy.today
        link
        fedilink
        English
        479 months ago

        Mainly conflicts with mDNS. However it’s shitty IMHO that the mDNS spec snarfed a domain already in widespread use, should have used .mDNS or similar.

        • xcjs
          link
          fedilink
          English
          99 months ago

          That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.

      • @ShortFuse@lemmy.world
        link
        fedilink
        English
        4
        edit-2
        9 months ago

        I’ve also used .local but .local could imply a local neighborhood. The word itself is based on “location”. Maybe a campus could be .local but the smaller networks would be .internal

        Or, maybe they want to not confuse it with link-local or unique local addresses. Though, maybe all .internal networks should be using local (private) addresses?

      • r00ty
        link
        fedilink
        19 months ago

        Hmm, the only issue I had was because it was using the DoH (which I don’t have a local server for). Once I disabled that, it was fine.

  • @Wilzax@lemmy.world
    link
    fedilink
    English
    409 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
        59 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

        • @friend_of_satan@lemmy.world
          link
          fedilink
          English
          149 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.

          • @Wilzax@lemmy.world
            link
            fedilink
            English
            59 months ago

            Ah good point. I guess a future-proofed guarantee that the domain will never be used externally would be easier to use than trying to somehow configure my DNS to never update specific addresses.

        • Magiilaro
          link
          fedilink
          English
          109 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.

          • @aesthelete@lemmy.world
            link
            fedilink
            English
            49 months ago

            I agree that this is a good idea, but I wanted to add that if someone owns a domain already, they can also use that internally without issue.

            If you own a domain and use Let’s Encrypt for a star cert, you can have nice, well secured internal applications on your network with trusted certificates.

            • Magiilaro
              link
              fedilink
              English
              29 months ago

              That is great when using only RFC 1918 IPv4 addresses in the network, but as soon as IPv6 is added to the mix all those internal only network resources can becomes easy publicly available and announced. Yes, this can be prevented with firewalling but it should be considered.

        • @patrick@lemmy.jackson.dev
          link
          fedilink
          English
          29 months ago

          If you just run a personal private network, then yea pick anything because you can change it fairly easily. Companies should try to stick to things that they know won’t change under them just to avoid issues

    • @Voroxpete@sh.itjust.works
      link
      fedilink
      English
      209 months ago

      Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won’t go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It’s the URI equivalent of 192.168.0.0/16.

    • Melllvar
      link
      fedilink
      English
      79 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.

      • KillingTimeItself
        link
        fedilink
        English
        29 months ago

        the only losers in this situation are people that are squatting on my rightfully pirated domain names!

    • @Monument@lemmy.sdf.org
      link
      fedilink
      English
      39 months ago

      Well, I just realized I completely goofed, because I went with .arpa instead of .home.arpa, due to what was surely not my own failings.

      So I guess I’m going to be changing my home’s domain anyway.

    • @subtext@lemmy.world
      link
      fedilink
      English
      19 months ago

      It was just always so annoying having to go into the iPhone keyboard punctuation twice for each domain

  • @Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    19
    edit-2
    9 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
    HTTP Hypertext Transfer Protocol, the Web
    HTTPS HTTP over SSL
    IP Internet Protocol
    SSL Secure Sockets Layer, for transparent encryption
    TLS Transport Layer Security, supersedes SSL
    VPN Virtual Private Network

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

    [Thread #910 for this sub, first seen 8th Aug 2024, 09:05] [FAQ] [Full list] [Contact] [Source code]