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

    • deadbeef79000@lemmy.nz
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      For the same reason you use RFC provided private IPv4 ranges.

      RFC 1918 reserves three IPv4 private address ranges: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These ranges are not publicly routable on the global Internet.

      Because there is a standard.

      Also, there is nothing stopping lan. getting registered as a TLD.

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

        Except that isn’t really a fair comparison. Private ranges aren’t any more complicated than public ranges so it doesn’t impact me when using IPv4 private IPs.

        .home.arpa is one of the most “designed by committee” domains I have heard in my life. It is way longer than .lan and defeats the point of local domains to begin with. I might as well use a public domain instead. .lan was around long before the standard and will be around long after

        If .lan becomes a TLD (it won’t) I can always go though and change it to something like lan1 or .mylan both of which would be shorter and easier to type