pi-hole-unbound-wireguard VS RPi-Docker-Server-Setup

In addition follow this until you get to the WireGuard install and install PiVPN instead: https://github.com/notasausage/pi-hole-unbound-wireguard.

I installed PiHole with Unbound, following this guide: https://github.com/notasausage/pi-hole-unbound-wireguard and after those, I also installed wireguard. Everything was working so far, but when I entered via ssh to the raspberry pi, to enable NFS shares there, it started having problems resolving the domains:

You navigate to the dns page of pi hole and input the static IP of your Pihole. Again doesn’t matter if you are wired or wireless. I love this guide: https://github.com/notasausage/pi-hole-unbound-wireguard. I use everything up to the WireGuard instructions and just use piVPN because I think it’s a better solution and I still use WireGuard!

I used guide: https://github.com/notasausage/pi-hole-unbound-wireguard

Using WireGuard or some other solution? Man - with a few pi’s, it was super simple. I used this guide as a guide: https://github.com/notasausage/pi-hole-unbound-wireguard For the server side set up. But when it came to the WireGuard piece I installed piVPN for WireGuard. Worked first time.

I also prefer in combo with WireGuard. There are some good tutorials out there. See this start to finish guide for setting up locally Pihole +Unbound +WireGuard or, even easier, this docker-compose tutorial called WireHole. If you want to go the cloud-based route there are a bunch of options. See this Cloudblock tutorial. It looks like it is still being maintained.

notasausage/pi-hole-unbound-wireguard: Turning your Raspberry Pi into an ad-blocking VPN with built-in DNS resolution using Pi-Hole, Unbound & WireGuard. (github.com)

I followed parts from this GitHub Repo. Though it adds things like cloudflared & autoupdating adlists, you can probably just skip/remove the stuff you don’t need/want.