Messages

Thank you very much! Works perfectly. Much more straightforward than what I had found online.

I have tried updating the dns server in the general settings to specify my pi-hole instance, but my dhcp clients are still receiving the default gateway ip for dns instead of my pihole ip. If I specify the pihole ip on the client, it will go to pihole and work normally.

I seem to remember this was a simple setting when using ISC, but I'm not absolutely clear how to do it now with Dnsmasq. I was under the impression the dns servers under the general settings would be sent to DHCP clients. Is DNS forwarding the way to do this? I'm sure I'm missing something simple. There is nothing complex about my setup.

Since the upgrade from ISC, I have just used the Unbound blocklists but want the pi-hole dashboard now for materics.

Hello everyone,

My wireguard clients are able to connect when tethered to my cell phone, but not when they are connected to wifi. They are able to connect to my local wireguard instance when on wifi, but not my remote wireguard instance. The stranger thing is that I could have sworn this configuration used to work fine, but perhaps I'm wrong. In essence I'm having a hard time even wrapping my head around what is the difference between connecting via tether vs. wifi. I have whitelisted my domains in zenarmor.

Thanks!

UPDATE! Both domains needed to be excluded in both zenarmor instances