I’ve got a modest homelab setup: a couple computers and a server with the pfsense router pointing all DNS queries to my pi hole on a Pi Zero W. The server exposes a few services via cloudflare tunnel. It’s been working pretty well.
Then I started setting up a server for a friend. It’s a big repurposed server board running proxmox and will eventually have a handful of VMs and LXCs, all on a network. It’s for his business, so I’m setting up Netbird on it for his half-dozen employees to be able to access it for fileshares and stuff. I’m connecting my desktop, too, so I can do sysadmin for him.
The trouble is that domain name resolution is getting hairy between my pihole and his netbird. Since it’s not my network, I can’t add my pihole as a DNS resource, but I do need to keep a connection to his network.
Anyone have any wisdom to share as to how to handle this properly and still be able to use my pihole for DNS filtering in my house?
StripedMonkey@lemmy.zip 1 hour ago
If you set up resources correctly on his netbird network it effectively is a split tunnel. You don’t have to route anything through it but his “file shares and stuff”.
I have a rather gnarly nested double nat within my house where the homelab is isolated behind it’s own separate firewall and have some limited resources on both. It’s been perfectly serviceable.
I believe I have a resource of
*.whathaveyou.neton the netbird gateway inside the network and no default route. If you do have that default route I believe you can have it as a separate resource and disable it.Self-hosted netbird is pretty incredible to be honest.