this post was submitted on 09 Feb 2026
35 points (97.3% liked)

Selfhosted

56229 readers
1063 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

So I have some services and wireguard running locally on a "home" network. I also have wireguard, a DNS resolver, and a reverse proxy set up on a remote server. Since I don't want to expose the home IP to the public, to access my services I connect to the VPN on the remote, which then forwards my request home. But this means that when I'm at home, connecting to my local services requires going out to the remote. Is there some way to have the traffic go over the switch when at home, but go over wireguard when away, without having to manually switch the VPN on/off?

I could move the DNS resolver (which handles the internal names for the services) from the remote to the home server. But then similarly every DNS request will need to go through both the remote and home servers, doubling the hops. I'd like to use my own DNS server at all times though, both at and away from home. Which tradeoff seems better?

edit: thanks for all the suggestions, I'll look into some of these solutions and see what works best

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

My Setup:

OpenWRT Router: wireguard server, backup DNS

NAS: Main DNS Server - pihole, no wireguard

VPS: Client - Endpoint 10.1.99.0/24, 192.168.2.0/24

Phone: Client - Endpoint 0.0.0.0/0, ::/0

10.1.99.0 clients can talk to 192.168.2.0 clients and back and forth. The NAS can talk to anyone, anyone can talk to the NAS. Any new client can talk to anything.

They all use the NAS for DNS, so they all resolve hostnames and domain names.

why not dns on the router?

I didn't like the unbound/adblock gui on Openwrt. I like pihole more. Personal pref.

[–] nymnympseudonym@piefed.social 1 points 7 hours ago

I too run a PiHole in an RPi, physically plugged in to my OpenWRT router