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

  • 𝘋𝘪𝘳𝘬@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 hours ago

    The de-facto standard for LAN-only domains is .local. The officially endorsed/standardized TLD is .internal.

    If you use your own DNS server and CA, you can literally set up whatever you like. You could even tell your DNS server to resolve example.com to your local IPs.

    My router – a Fritzbox – automatically sets up hostname.fritz.box for all connected hosts but HTTP only. If your router does the same, you could use those and have your CA issue certificates accordingly.