Thanks for all your work on Pi-Hole, the new Web interface is vastly more complex and I see features a bunch of debugging tools. It must have taken a while to write!
My Pi-Hole is fully up to date and running on a fully-patched Debian 12 VM (not in a container).
Since I've disabled and stopped lighttpd and added a "Custom DNS Server" for my upstream DNS it seems to be fully functional from PCs on my network.
My Android Devices still refuse to connect to WiFi, saying "Can't provide Internet" when the internet has never been unavailable. The problem is DNS.
I have always blocked Google DNS servers at my network firewall (you'll notice 8.8.8.8 can't be used to resolve domains in the diagnostics but this is a false-positive. It is not causing the problem as it has not changed in years).
Actual Behaviour:
Android Devices still won't connect to WiFi after Pi-Hole configuration was fixed after upgrade. I've tried rebooting them to no effect.
The problem might be that I have 3 different internal (private) networks.
It seems dnsmasq configuration in Pi-hole has changed so that it now ignores queries from "non-local" networks. Can someone please help me configure it to permit from the 3 subnets I need it to answer to?
The documentation states that the dnsmasq option "local-service" is now enabled.
but I can't find that option in the UI.
How can I reconfigure FTL to respond to "non-local" DNS queries please?
There does not seem to be a reverse option I could put in an /etc/dnsmas.d/myconfig.conf file to undo it!
This is a major version change (V5 to V6) that is a complete rewrite of much of the code. This work has been in progress for over 4 years, and was beta tested for a significant period of time prior to release as V6 (since October 2023).
