Imo it’s quite nice to not have a public domain like cloud.example.com which is much longer and all the gold ones are taken anyway.

Putting these local ones in my dns server is no issue, but getting https to work seems like a pain. I set up caddy to use its own certificate authority, but even when installing the root certificate to windows, many programs still don’t truth it and most of them don’t show a useful error message. Additionally getting them to trust the certificate is fiddely and then try to explain that to your mom so she can use my cloud.

All this makes me thing about switching back to public subdomains so I can get lets encrypt certificates

  • Taasz/Woof@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    I use .lan for most local stuff, since it’s local only I don’t bother with HTTPS at all.

    Anything that needs it like Vaultwarden just goes on a real domain so a letsencrypt wildcard cert works.

  • lemmyvore@feddit.nl
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 days ago

    like cloud.example.com which is much longer and all the gold ones are taken anyway.

    You can try getting a shorter domain from a ccTLD. I’ve probed my country’s whois for 1-3 digit domains once on a whim and stumbled across one that was free.

      • lemmyvore@feddit.nl
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day ago

        Just a shell script running whois in a loop and looking at the output, with random sleep intervals in-between. Left it running overnight, 1100 domains is not a lot (I also checked the versions with with zero padding).

        I was only able to find cheat five character domains

        Probably depends a lot on the country TLD.

  • barnacles@lemmy.zip
    link
    fedilink
    English
    arrow-up
    39
    arrow-down
    1
    ·
    3 days ago

    As far as I’m aware, the only “local” domains are the ones reserved in the RFC, e.g. home.arpa

    Everything else is just a public domain you don’t own, or not a domain. Using a domain that you don’t have authority over carries risks, even if you think you’ve kept everything local. Just use a real domain that belongs to you.

  • zelifcam@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    37
    ·
    3 days ago

    Many years ago I settled on a real domain using reverse proxies / dns overrides so that local and remote work the same. Workflow has been working for well over a decade.

    • davad@lemmy.world
      link
      fedilink
      English
      arrow-up
      29
      ·
      3 days ago

      This. Also, if you don’t want to allow remote access, you can still use a real domain. It’s possible to use public DNS only for the ACME challenge, and local DNS for everything else.

      • asap@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        13 hours ago

        You don’t even need public DNS at all. My public domain points all records to 192.168.1.1, and Caddy registers certs without any issues.

      • plateee@piefed.social
        link
        fedilink
        English
        arrow-up
        16
        ·
        3 days ago

        I have a public domain, and use a subdomain for my homelab - .lab.myfqdn.com. I do public DNS ACME challenges for a wildcard *.lab.myfqdn.com.

        It’s a double bonus because I don’t have SSL cert records leaked to the internet, and I can also browse internal services on my devices and family devices without having to do weird stuff with SSL cert trusts.

      • lemmyvore@feddit.nl
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        That’s the most common sense approach, so you don’t run into situations where your Internet is down and you’re trying to resolve a LAN IP through an unreachable public server. Records may or may not be cached anymore on the local when the connection goes down.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    3 days ago

    The certificate problem that you are running into is the same one I ran into and why I got a domain.

    Now I have Traefik get a wildcard cert from LE and no more issues.

    I don’t have anything publicly accessible so my public DNS record points to an IP on my lan.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 days ago

      Can I recommend that you move that record to the local DNS? Assuming your router’s firmware has this feature and you can access it.

      Private IPs in public DNS are associated with certain types of attacks and they get filtered by some DNS servers, routers or ISPs so you may run into intermittent “unexplained” hiccups.

      Secondly, if your internet ever goes down in the middle of the night and the records expire from the local DNS cache by morning, you won’t be able to resolve anything on your LAN anymore. Which is a pity because it’s unnecessary, your local setup can work fine independent of the internet connection.

      Last but not least, there are actors out there that use a variety of methods to gather information about the infrastructure behind each domain and the least such information you put out there, the better.

      Run your domain through DNS Robot to get an idea.

      • slazer2au@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        I have adguard home to intercept the requests. Private IPs in public DNS is a non issue. We did it quite a bit at the ISP I worked at.

        • lemmyvore@feddit.nl
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          Were you doing split DNS? The average registrar DNS or end-user DNS provider is not typically split-capable.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      2 days ago

      Why use Traefik? You could just put a reverse proxy on each device and then automate it all with a simple script

  • cow@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 days ago

    I use .internal, setup a self-hosted certificate authority providing ACME to servers. The certificate is set to only be valid on .internal domains and not the entire internet and enrolled on my phone and computers.

    • fuckoffplzkthx@lemmy.zip
      link
      fedilink
      English
      arrow-up
      8
      ·
      2 days ago

      I’ve never liked this approach - having to enroll certs on every machine always seemed tedious and it’s why I just “dealt with” having HTTPS errors internally for years.

      Honest question, why not set up a reverse proxy that uses Let’s Encrypt? It will handle internal domains if configured appropriately, and then you only have to configure at the proxy and DNS level.

      • cow@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        I’ve never liked this approach - having to enroll certs on every machine always seemed tedious and it’s why I just “dealt with” having HTTPS errors internally for years.

        You only have to do it once per machine and I use NixOS a lot so its easy to just add to a module imported by every system. On other Linux systems it’s just putting the pem file somewhere in /etc/ and running a command to reload it. Android cell phones were pretty easy but I forget the exact details.

        Honest question, why not set up a reverse proxy that uses Let’s Encrypt?

        I have multiple of those for public services. Because I don’t want to expose every service to the internet for HTTP-01 and can’t use DNS-01 due to how my nameservers are set up, this makes sense. Other advantages are not needing to distribute DNS update keys to every single server for security reasons and having shorter domains.

  • Y33tMaster69@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    All of my services are currently local only so I just run http on all of them. I do still like being able to use a hostname instead of memorizing port numbers for everything so I do use *.home.lan.

    Eventually I will be exposing some services but right now I am behind cgnat and don’t have a decent router to support modern ipv6 yet.

  • Shimitar@downonthestreet.eu
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 days ago

    Using self signed as a route that it’s not going to work after you factor in service specific apps that refuse your self signed certs, phones where installing those certs is a pain, and the overall WAF where installing those certs might just put off family users.

    Add in the mix the new Android 17 fucking “feature” where apps need special permissions to access the local network … (Yeah, Dav5x, home assistant, even Firefox stopped working on my on Android until I figured this out after upgrading to 17). I will write a post on this topic later on today.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      Self signed also makes it easy for someone to compromise https on your network

      If you need to use a self sign certificate make sure to add name restrictions in the root so that it can’t be used for public domains

  • Reannlegge@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 days ago

    I have my own domain with a cert so it is (service).reannlegge.ca in caddy, I don’t really let many of my things out onto the web without the VPN but it is nice having the https and not having to see the this site may not be secure for almost everything I do.

  • boudica@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    x.home.arpa was made for this situation. I’ve been able to use caddy’s certificate with no issues.

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    2 days ago

    Don’t use TLS with local domains like lan. It is fairly risky and prone to issues.

    They are fine for ssh and other services not dependent on TLS though