• conorabA
    link
    fedilink
    English
    arrow-up
    39
    ·
    9 months ago

    A good move!

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

      • sir_reginald@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 months 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.

    • Atemu@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 months 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.