• xcjs
      link
      fedilink
      English
      arrow-up
      30
      ·
      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. 😅

        • xcjs
          link
          fedilink
          English
          arrow-up
          10
          ·
          3 months ago

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

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

        • Supermariofan67
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 months ago

          Accessing printers? Resolving hostnames of internal hosts? I can’t imagine having a lan without mDNS

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

    • 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.

    • dhtseany@lemmy.ml
      link
      fedilink
      English
      arrow-up
      16
      arrow-down
      7
      ·
      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
          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
          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

      • 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.