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

  • Willoughby@piefed.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    10 hours ago

    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.