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

  • zelifcam@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    18
    ·
    3 days ago

    Many years ago I settled on a real domain using reverse proxies / dns overrides so that local and remote work the same. Workflow has been working for well over a decade.

    • davad@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      3 days 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.

      • asap@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        16 hours ago

        You don’t even need public DNS at all. My public domain points all records to 192.168.1.1, and Caddy registers certs without any issues.

  • Y33tMaster69@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    All of my services are currently local only so I just run http on all of them. I do still like being able to use a hostname instead of memorizing port numbers for everything so I do use *.home.lan.

    Eventually I will be exposing some services but right now I am behind cgnat and don’t have a decent router to support modern ipv6 yet.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    3 days ago

    The certificate problem that you are running into is the same one I ran into and why I got a domain.

    Now I have Traefik get a wildcard cert from LE and no more issues.

    I don’t have anything publicly accessible so my public DNS record points to an IP on my lan.

  • cow@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    I use .internal, setup a self-hosted certificate authority providing ACME to servers. The certificate is set to only be valid on .internal domains and not the entire internet and enrolled on my phone and computers.

  • boudica@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 days ago

    x.home.arpa was made for this situation. I’ve been able to use caddy’s certificate with no issues.

  • Reannlegge@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    I have my own domain with a cert so it is (service).reannlegge.ca in caddy, I don’t really let many of my things out onto the web without the VPN but it is nice having the https and not having to see the this site may not be secure for almost everything I do.

  • 𝘋𝘪𝘳𝘬@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days 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.

  • lambalicious@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    3 days ago

    The need for “proper domains”, where “proper” nowadays seems to mean “Trump-approved”, is an important risk, because then the identity of your homelab depends on the DNS and SSL cartel. It’s one of the reasons I distrust the Gemini protocol and consider it a raw downgrade from Gopher (and from HTML, for that matter).

    If home.arpa is the way to go local, then it’s the way to go local.