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

  • davad@lemmy.world
    link
    fedilink
    English
    arrow-up
    25
    ·
    1 day 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.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 hours 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.

    • plateee@piefed.social
      link
      fedilink
      English
      arrow-up
      14
      ·
      23 hours 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.