I am having a problem with pihole and mullvad
from osanna@thebrainbin.org to selfhosted@lemmy.world on 14 Feb 11:43
https://thebrainbin.org/m/selfhosted@lemmy.world/t/1419452
from osanna@thebrainbin.org to selfhosted@lemmy.world on 14 Feb 11:43
https://thebrainbin.org/m/selfhosted@lemmy.world/t/1419452
Hello
So I set up pihole on my new raspi, and when i set custom dns server (local address, 192.168.x.x) on mullvad, it stops resolving. It resolves for about 10-15 seconds, but then after that, it stops resolving.
The pihole works without mullvad, and mullvad works without custom dns being set up. I have tried on multiple machines (mac)
Anyone experienced this and anyone know of a fix?
I will probably get in contact with mullvad and see if they have any insight.
TIA
#selfhosted
threaded - newest
btw, I have set local connection to true
Doesn’t your local DNS has to reach out to another DNS to query yet unknown addresses, causing an infinite loop as it’s now told to reach out to itself?
nah, the pihole is set to every dns available minus google for external addresses.
https://en.wikipedia.org/wiki/Split_tunneling
https://mullvad.net/en/help/split-tunneling-with-the-mullvad-app
https://discourse.pi-hole.net/t/split-dns-for-multiple-routers-with-same-local-domain-name/64192
What does the command
dig debian.orgreturn?interestingly, it resolves it. hmm. I don't know. I tried a few domains after a while of having the custom dns set up, and it resolved all of them.
Which DNS server is hitting first your local pihole or the remote mullvad one?
I have had issues in the past with bad SD cards on my pi-hole that cause it to stop working after a few minutes. I know you said it works fine without Mullvad, but was that just a quick verification or an extended long-term test with traffic?