Selfhosted

39435 readers

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

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Traefik for two domains, one internal and one external (lemmy.dbzer0.com)

submitted 7 months ago by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

So, at the moment I'm using Nginx Proxy Manager, but lately I started seeing it moving slower and slower and even though I tried traefik some time ago, I didn't manage to make it work.

Anyway, I want to start using traefik again, but I want to use it like this:

I want to access all my services/containers in my LAN through http (port 80) on something like sub.mylan.home
I want to access some of my services over the internet through https (port 443) on sub.mydomain.com

I know this is possible, but I don't get the hang of the configuration. Somone care to share some tips?

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

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

Caveat emptor, split DNS can cause issues down the line that are a proper nightmare to debug.

Don’t do it unless you a) understand what is happening on your network when you config it this way b) have the tools and ability to verify it is working like you think it should and troubleshoot when things eventually break and c) can exercise enough control over your network to make sure all DNS resolution in your LAN happens the way you think it should.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

Perhaps I'm misunderstanding the term but I don't think what I described is split DNS. Split DNS is when the same DNS server resolves a name differently depending on the IP address of the client.

In the scenario I described the DNS servers involved do not discriminate, they always resolve the same names the same way.

The ability to discriminate at the client (to search specific DNS servers for specific domains) is not split DNS (although it's often incorrectly called that).

If this is what you meant then yes, it can be a bit of a headache. For example if you need to resolve local LAN names (.lan or .local), Tailscale names, and Docker names at the same time inside a container it can get a bit hairy.

[–] [email protected] 1 points 7 months ago

You are right, I wanted to address two different issues and they sort of merged together in my head.

Carry on ;)