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

  • e0qdk@reddthat.com
    link
    fedilink
    English
    arrow-up
    27
    ·
    11 hours ago

    .internal was registered for private use by ICANN in 2024

    (If you’re going to use something other than .home.arpa, it should be that one.)

    • barnacles@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      11 hours ago

      Nice one, wasn’t aware of that. Internal sounds like a nice option in that context, especially outside of home networks