63

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

you are viewing a single comment's thread
view the rest of the comments
[-] slazer2au@lemmy.world 13 points 2 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.

[-] lemmyvore@feddit.nl 4 points 1 day ago

Can I recommend that you move that record to the local DNS? Assuming your router's firmware has this feature and you can access it.

Private IPs in public DNS are associated with certain types of attacks and they get filtered by some DNS servers, routers or ISPs so you may run into intermittent "unexplained" hiccups.

Secondly, if your internet ever goes down in the middle of the night and the records expire from the local DNS cache by morning, you won't be able to resolve anything on your LAN anymore. Which is a pity because it's unnecessary, your local setup can work fine independent of the internet connection.

Last but not least, there are actors out there that use a variety of methods to gather information about the infrastructure behind each domain and the least such information you put out there, the better.

Run your domain through DNS Robot to get an idea.

[-] slazer2au@lemmy.world 2 points 1 day ago

I have adguard home to intercept the requests. Private IPs in public DNS is a non issue. We did it quite a bit at the ISP I worked at.

[-] lemmyvore@feddit.nl 1 points 1 day ago

Were you doing split DNS? The average registrar DNS or end-user DNS provider is not typically split-capable.

[-] possiblylinux127@lemmy.zip 0 points 16 hours ago

Why use Traefik? You could just put a reverse proxy on each device and then automate it all with a simple script

[-] slazer2au@lemmy.world 4 points 15 hours ago

??? Traefik is a reverse proxy

[-] possiblylinux127@lemmy.zip 0 points 6 hours ago

How many instances are you running. Having a single point of failure seems risky to me

[-] slazer2au@lemmy.world 2 points 5 hours ago

Its a home lab spof are totally fine. I do need better uptime then Github but not 3 or 4 9s.

this post was submitted on 19 Nov 2026
63 points (100.0% liked)

Selfhosted

63971 readers
1430 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS