• @[email protected]
    link
    fedilink
    English
    391 year ago

    A good move!

    I’m surprised they didn’t codify “.lan” though since that one is so prevalent.

    • @fishpen0
      link
      English
      91 year ago

      deleted by creator

      • @sir_reginald
        link
        English
        11 year ago

        I think needing a VPN to access the internal network is a good practice. And if you’re going to be used a VPN anyway, I don’t see why you wouldn’t use a “fake” TLD like .lan for internal stuff, after all it’s just simple DNS rules.

        • @fishpen0
          link
          English
          11 year ago

          deleted by creator

    • Atemu
      link
      fedilink
      English
      31 year ago

      It’s used in many cases where the machine may not be on the LAN and LAN is a technical term. “Internal” is not and to me signifies that it’s “not public” aswell as probably managed by someone, well, internally at the entity you’re with.