• r00ty
    link
    fedilink
    1041 month ago

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

    • xcjs
      link
      English
      301 month 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
          English
          101 month ago

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

      • r00ty
        link
        fedilink
        31 month 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
          English
          51 month ago

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

          • r00ty
            link
            fedilink
            21 month 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.

    • @[email protected]
      link
      fedilink
      English
      261 month 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
        link
        fedilink
        English
        71 month 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?

    • @[email protected]
      link
      fedilink
      English
      101 month ago

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

      • @[email protected]
        link
        fedilink
        English
        451 month 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
          English
          81 month 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.

        • xcjs
          link
          English
          41 month ago

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

        • @[email protected]
          link
          fedilink
          English
          21 month 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

      • @[email protected]
        link
        fedilink
        English
        4
        edit-2
        1 month 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?

    • @[email protected]
      link
      fedilink
      English
      51 month ago

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

      • r00ty
        link
        fedilink
        11 month 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.