• xcjs@programming.dev
      link
      fedilink
      English
      arrow-up
      30
      arrow-down
      1
      ·
      3 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. 😅

    • chrisbit@leminal.space
      link
      fedilink
      English
      arrow-up
      26
      ·
      3 months ago

      It’s also second only to .com in terms of query volume in ICANN’s Magnitude statistics with 980 mil vs .internal’s 60 mil. Not sure if that makes it a de facto standard, but it’s close.

      • anytimesoon@feddit.uk
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 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
          arrow-up
          3
          ·
          3 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
      arrow-up
      16
      arrow-down
      8
      ·
      3 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
        arrow-up
        47
        arrow-down
        1
        ·
        3 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@programming.dev
          link
          fedilink
          English
          arrow-up
          9
          arrow-down
          1
          ·
          3 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.

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

          You mean mDNS/Zeroconf are using a tld that was already being used.

        • xcjs@programming.dev
          link
          fedilink
          English
          arrow-up
          4
          ·
          3 months ago

          Macs aren’t the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.

        • ChapulinColorado@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 months ago

          Even on windows sometimes depending on the target host, I’ve had to type host.local. (Final dot to do exact match) instead of host.local

          This didn’t seem to affect other domains. I’m assuming it was due to special handling of .local

        • ayyy@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          mDNS hasn’t been a just-Apple thing for decades. Do you still call it Ren-dess-voos like the Gaston character in Beauty and the Beast?

      • ShortFuse@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        3 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?

    • UberMentch@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 months ago

      I’ve had issues with .local on my Android device. Straight up doesn’t work. I had to change to .lan

      • r00ty@kbin.life
        link
        fedilink
        arrow-up
        1
        ·
        3 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.