this post was submitted on 10 Sep 2024
15 points (89.5% liked)

Selfhosted

39937 readers
395 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
15
DNS Management Advice (lemm.ee)
submitted 1 month ago by ___@lemm.ee to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

I’m running opnsense on proxmox with some lxc containers and docker hosts.

I’ve never done internal DNS routing, just a simple DMZ with Cloudflare proxies and static entries for some external services. I want to simplify things and stop using my IPs from memory internally.

For example, I have the ports on my docker hosts memorized for the services I use, only a couple mapped hosts in opnsense, but nothing centralized.

What is the best way to handle internal DNS name resolution for both docker and the lxc containers? Internal CA certs? External unroutable (security)?

Any tips and setups appreciated.

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 4 points 1 month ago* (last edited 1 month ago) (1 children)

Focus on DNS for the host machine and it's port mappings, not the individual containers.

If you're instead asking "How can I easily map a DNS name to service and port?", then you want a reverse proxy on your host machine, like nginx (simplest) or Traefik (more complex, but geared towards service discovery and containers).

In the latter scenario you setup a named virtual host for each service that maps back to the service port exposed for your containers. Example: a request for jellyfin.localdomain.com points to the host machine, nginx answers the request and maps the host name in the request, then proxies your session to the container.

It's copy and paste for the most part once you get the first one going unless you're dealing with streaming.

If you're running a flexible platform on your router like OpenWRT, you could also do some port forwarding as a means to achieve the same thing.

[–] ___@lemm.ee 1 points 1 month ago

This is what I was think also. Just let the host rproxy the requests and just map the dns to the host in opnsense.