Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
_Sites to load quickly, no lag
-Debian 12
-hardware: Dell Wyse 7010 thin client
Backup Pihole instance running on a Raspberry Pi Zero v 1.1
Actual Behaviour:
I know PiHole should not affect my internet speeds, but I feel like something is not right. Very much probable it is user error on my part. Some sites take painfully slow to load. As an example, Netflix on a smart TV would not load. Even after adding (.|^)netflix.com$ as a Regex allow, I am still experiencing overall poor network performance. Files take forever to load in my work Slack. Reddit often takes a long time to load.
I had unbound installed on both PiHoles, but I uninstalled on both to see if that would help. Dell Wyse is using Cloudfare DNS (ip4 and 6) as upstream DNS. Rasp pi is set to Google ip4 and 6.
Backup pihole: I actually could not upload this debug token. I got this error, perhaps this is part of the problem?:
Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
Does anytihing jump out on the main pihole debug? I can post the backup debug link when I get the above error resolved.
I was getting A LOT of Connection errors: failed to send UDP request (Network unreachable). I realized Ipv6 support was NOT enabled on my router so I disabled the Ipv6 upstream DNS servers. Hopefully this will improve things.
Curl still cannot upload by debug token from the Rasp Pi, not sure what is going on there.
Your devices will get the ip you specify under "DNS Server 1" and "DNS Server 2" as their DNS server provided from the router by DHCP.
In the second image, the dns director does not seem to be set up optimally for use with a Pi-hole.
If the Pi-hole's ip is entered under "user defined dns 1", and global redirection is set to "User defined 1", DNS director will catch requests from devices that ignore the DHCP provided DNS server and send them to your Pi-hole.
(Setting it to "router", as in your linked post, instead of "User Defined 1" will instead send any of those queries to the DNS server specified in the router's wan settings. If you have the wan dns set to your Pi-hole it can cause DNS loops).
The Pi-hole should still be added to the client list and set to "no redirection" to ensure it can reach its upstream dns servers.
On 3004.388.8_4 I would set up DNS director like this (change ip to that of your Pi-hole):
