Comment on Setup a DNS server on a dynamic public ip
ClickyMcTicker@hachyderm.io 9 months ago
@papelitofeliz
VPN for sure:
1. Set up both locations with Dynamic DNS providers. DuckDNS is free, but if you’re building infrastructure you may as well buy your own domain and set it up through that (Namecheap is what I use and recommend).
2. Set up a Wireguard tunnel between both locations. Do *not* specify an endpoint for either. You could specify endpoints to boost security (barely), but it will cause your system to fail during IP changes, for the duration of the TTL.
ClickyMcTicker@hachyderm.io 9 months ago
@papelitofeliz
3. Set up your PiHole on a static private IP.
4. Ensure both sites can route across the tunnel. Based on your experience level and scope, dynamic routing is not recommended or necessary, which means static routes. Point a route for each side’s subnet to the Wireguard tunnel IPs so your firewalls know how to reach and respond to each other across the tunnel.
5. Configure your devices to use PiHole for their DNS, via DHCP ideally.
papelitofeliz@lemmy.world 9 months ago
I didn’t look anything up yet. But can the wireguard tunnel be setup on the router level (I have a cheap Mikrotik) or as a network service? So clients don’t have to install custom stuff
bless@lemmy.world 9 months ago
Yes