Please see link to my debug logs. My devices (laptop, TV) are connected to wifi but with NO internet. When I disable blocking from Pi-Hole, the devices connect to the internet. Here's the head scratcher, my work laptop, phone, etc.. are connected to wifi with internet access. Any assistance is greatly appreciated.
From your debug log, no port 53 traffic is being processed by the Pi:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] upresvonver.000webhostapp.com is us-east-1.route-1.000webhost.awex.io.
145.14.144.64 on lo (127.0.0.1)
[✓] No IPv4 address available on eth0
[✗] Failed to resolve upresvonver.000webhostapp.com on wlan0 (192.168.1.2)
[✓] doubleclick.com is 142.250.176.14 via a remote, public DNS server (8.8.8.8
From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
I enabled blocking on PiHole. On laptop giving me issue. I went to aol.com and I get a statement this device is blocked by access control in the router (pi-hole)
And just to completely waste your time reading this: is aol is your blacklist, or is it being blocked by the gravity database in the query log? I assume no, because that would be very visible.
So do I understand that it thinks this website is .22? I would guess this is a dns resolution issue.
Negative, AOL is NOT on my blacklist or being blocked (verified on PC and phone) w/ Pi-Hole blocking enabled. yeah it's weird that it's blocked by my netgear router
Disregard above use case
New use case:
Update macOS > unable to connect to internet (When Pi-Hole blocking is enabled).
When I disable blocking in Pi-Hole, I'm able to view the latest update for Mac.
There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47
DNS configuration
resolver #1
nameserver[0] : 192.168.1.1
if_index : 6 (en0)
flags : Request A records
reach : 0x00020002 (Reachable,Directly Reachable Address)
resolver #2
domain : local
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300000
resolver #3
domain : 254.169.in-addr.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300200
resolver #4
domain : 8.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300400
resolver #5
domain : 9.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300600
resolver #6
domain : a.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300800
resolver #7
domain : b.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 301000
The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net