Selfhosted

40218 readers

1082 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Ideas wanted (lemmy.world)

submitted 1 year ago by TvanBuuren@lemmy.world to c/selfhosted@lemmy.world

24 comments fedilink hide all child comments

Hey all. Ive been hosting some software for a while now, some private, some public stuff.

Recently ive gotten myself a domain name, and i'm trying to come up with a good way to have access to both the public AND the private on the same URL. Simpleton that i am i thought about putting the public in an inline frame with a banner with links at the top, but im sure there are better ways.

Any ideas how to do this from this community?

you are viewing a single comment's thread
view the rest of the comments

[–] midas@ymmel.nl 14 points 1 year ago (4 children)

Not sure if I completely understand but I think you want public service 1 accessible on subdomains s1.domain.com and internal service 2 on s2.domain.com?

Just point the A record for s2 to an internal ip address (or a tailscale ip). The only thing dns does is translate a (sub)domain to an ip address. So outside of your network s2.domain.com wouldn't resolve but inside your network it would.

[–] BlackEco@lemmy.blackeco.com 4 points 1 year ago

That's what I did:

There is *.selfhosting.domain.tld that points to my router's IP address, which then redirects to an nginx+certbot reverse proxy
Then there is *.local.domain.tld that points to my local IP with Caddy

The only challenging part was to configure Caddy to issue SSL certificates using the DNS challenge since *.local.domain.tld isn't exposed to the outside world.

[–] EncryptKeeper@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

Or just use one, and then run a local DNS resolver like pihole or AdGuard home and just make a record for the same host locally. The local DNS resolver will resolve the local request before it reaches the public DNS.

[–] teuto@lemmy.teuto.icu 1 points 1 year ago

I prefer to use a local DNS for internal services just so there is less publically available information about my internal network. No need to let everyone know what address space I use or which vlan certain services are on. Also means you don't have to wait for public DNS servers to update.

[–] TvanBuuren@lemmy.world 1 points 1 year ago (1 children)

subdomains would work, though ive never worked on it without a gui. Time to do some learning i guess :)

[–] ThreeHalflings@lemmy.world 1 points 1 year ago

OK, I didn't read before answering, probably ignore my answer below but I'll leave it up incase someone learns something from it.