Please follow the below template, it will help us to help you!
Expected Behaviour:
Change routers, applied settings the same as the old, pi.hole should function
Actual Behaviour:
Changed from a Netgear AC1750 to Linksys WRT32X and pi.hole no longer blocks despite settings being accurate.
Debug Token:
g6m9mjrz1k
Hello everyone,
First I must say how much I love the pi.hole project. It has been absolute fantastic having network wide ad blocking. I recently upgraded my router as mentioned above and changed the appropriate settings accordingly yet the pi.hole ceased blocking network wide. I never used it as my dhcp server just strictly my DNS and it functioned flawlessly on the netgear. Due to moving into a house from an apartment I needed more horsepower to cover more of the house hence the upgrade. Is there something about the linksys router that I am missing in some way? Has anyone else experienced something similar?
Thank you for your time and help and I will make sure to upload that debug token the minute I get home.
We have heard about similar issues in the past. Most often the new router did not support specifying an internal DNS server (i.e. any DNS server with 192.168....), hence either didn't accept the change at all or just ignored it. I don't know how the Linksys WRT32X handles this - I have been Googling around a bit but have found nothing that would give a clear yes or no on my assumption.
The commonly applied "fix" was to switch to Pi-hole's DHCP server altogether as this resolve drawbacks the router's firmware might have in this regard.
I kept running into the same problem. I pulled the logs from the router, and found that given that its firmware is based on OpenWRT, the logs kept indicating it was blocking those internal requests because it believed them to be a DNS Rebind attack because OpenWRT naturally blocks local DNS requests as you mentioned. I've been poking and prodding around the command line (I found you can ssh into the OpenWRT based series via the routers ip and the password you set up for its web portal) and I've been tinkering with various settings to some success albeit intermittent depending on device. And I'm much more familiar with Debian and APT than I am with Ash and BusyBox that the firmware uses. PSA the basic web portal for this device STINKS, so very few settings can be adjusted without the CLI and ssh.
I'll keep tinkering on my end but wanted to share what I found late last night and thank you for the wonderful software that is pihole!
