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

  • @redcalcium@c.calciumlabs.comEnglish
    7•2 years 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@c.calciumlabs.comEnglish
        1•2 years 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@lemmy.worldEnglish
      1•2 years 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
        9•2 years 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.

  • VerifiablyMrWonka
    6•2 years ago

    I just bought an actual domain and use that 😅

    As an added bonus, letsencrypt works with no effort.

  • @MangoPenguin@lemmy.blahaj.zoneEnglish
    5•2 years ago

    For local DNS home.arpa is I think what we’re ‘supposed’ to use, but I use .lan

    Only use another domain name if you actually have it registered, like myname.net or something. As a bonus you can then get a wildcard letsencrypt SSL cert for easy HTTPS.

  • @taladar@sh.itjust.worksEnglish
    5•2 years ago

    You shouldn’t use .local for your manually defined local domain names if you plan to ever use mdns/avahi/bonjour/zeroconf.

    • Mr_Figtree
      2•2 years ago

      And .box has been registered as a generic TLD now, so you could run into external .box domains.

      • PerhyteEnglish
        1•2 years ago

        Hopefully AVM gets to register fritz.box then, because they’ve been setting up their customers with that as their internal domain for ages…

  • KairuByteEnglish
    3•2 years ago

    *.internal.domain.name since ssl certs are easier to get when you’re using an owned domain name.

  • @iks@lemmy.worldEnglish
    1•2 years ago

    hostname.vlan.local.lan

    local.lan is the only fixed part of my fqdn’s

  • nsaobserverbot
    1•2 years ago

    fritz.box for the machines themselves because Fritz!BOX (although handed out by Pi-Hole),but .lan for anything going over the local proxy towards the same machine for TLS.

    Some machines use my custom domain name instead of .lan, if they need to be accessible from outside. So these last ones go directly over the local proxy internally, but automatically over CloudFlare Tunnel and Authentik when not at home. The proxy being Caddy.

    • Meow.tar.gz
      1•2 years ago

      That will work fine so long as you don’t need services like Avahi and mDNS.

  • Walter_EgoEnglish
    0•2 years ago

    i use my external zone name but have an internal view of the zone inside my lan so records point to local ips.