OK, so I have run into an issue from time to time where I will visit a site, and because it’s accessing an external site that PiHole Blocks to deliver content, pages and content won’t appear, now sometimes it’s not apparent that something has been blocked unless you dig into the inspector for the page, which can lead to a lot of drama and back and forth work trying to troubleshoot.
What I’d like to suggest is a (what I hope could be) simple interface in the PiHole Admin GUI, you’d enter a URL, and the PiHole would do a fetch in the background of the page (I know there are a couple command line Linux tools that can grab a page this way) and analyze the DNS requests being made from the unit during that page fetch.
Once the page completes loading, the console spits back a report not dissimilar to the query log, showing all DNS requests made while loading the page, and what was accepted and rejected, allowing the end user to White/Black list the domains directly from that page.
This differs from just querying the blocklist, as it checks sites that the end user may not be aware their domain is loading.
The pros I see in this is:
- it creates a sealed system for testing problematic pages,
- a detailed log could be generated and used for troubleshooting unusual behavior
- it eliminates any user end issues, allowing troubleshooting of an issue to eliminate the PiHole as a problem source
- it reduces time and troubleshooting from end users and administrators