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

  • lemmyvore@feddit.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    19 hours ago

    Having access to port 80 on the IP associated with a domain but not to the DNS raises some interesting questions. 🙂

    Unless it’s purely a matter of personal preference but I for one don’t see why you’d want to do HTTP-01 (as a self-hoster) unless forced. It can’t do wildcards, for one thing. And you need an A record pointing to your public IP, and if your public IP is dynamic you need to do DDNS, and open port 80 and so on. That’s a lot of moving pieces that make automation hard.

    Also, if you’re doing DDNS there’s a chance the DNS has some sort of API that might also work for certbot. Granted it’s not a given, I’ve seen registrars that offer a DDNS link but not something you’d call an actual DNS API.

    But anyway finding a decent DNS provider with a certbot-friendly API is not that hard.

    • frongt@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      19 hours ago

      The main use case is someone using a free subdomain. It’s not that uncommon.