There are many DNS names options. Which one do you use?

  • redcalcium
    link
    fedilink
    English
    19
    edit-2
    1 year ago

    According to IETF, you should only use .intranet, .internal, .private, .corp, .home or .lan for your private network ( RFC 6762 Appendix G ). Using other TLDs might cause issues in the future, especially since new gTLDs seems to show up every few months or so, which can collide with the TLD you use for your local network.

      • redcalcium
        link
        fedilink
        English
        2
        edit-2
        1 year ago

        Interesting, so this is the latest recommendation? Which is probably why I haven’t seen it in the wild yet, at least in my circles.

        Which means they probably going to cash out release gTLDs for .intranet, .internal, .private, .corp, .home and .lan soon…

    • @vegetaaaaaaa
      link
      English
      5
      edit-2
      1 year ago

      A problem with the .lan TLD (maybe others from this list) is that web browsers do not consider it a TLD when you type it in the address bar, and only show you the option to search for that term in your default search engine. You have to explicitly type https:// before it, to have the option to visit the URL.

      E.g type example.com in the address bar -> pressing Enter triggers going to https://example.com. Type example.lan -> pressing Enter triggers a search for example.lan using your default search engine.

      • distantorigin
        link
        fedilink
        171 year ago

        Little known trick–or perhaps everyone knows it and is quietly laughing behind my back–with Chromium browsers and Firefox (and maybe Safari, I’m not sure), you can add a slash to the end of an address and it will bypass the search.

        So, for example, my router on the LAN goes by the hostname “pfsense”. I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.

    • Kata1yst
      link
      fedilink
      21 year ago

      I can vouch for the fact that .local stopped working suddenly in most browsers a year or two ago, I was forced to migrate to .internal