Pi-hole should block ads while allowing devices internet access.
Actual Behaviour:
Every device on the local network works fine (all on WiFi), multiple phones and Windows 10 laptops.
The single exception to this is my Windows 10 pc. Initially it would connect but the speed would fluctuate wildly from minute to minute, and after multiple attempts at uninstalling the network adapter, updating drivers, renewing / releasing / dns flushing, it now more often than not just says "No internet, secured".
All settings are outwardly the same as those of my laptop, which works fine with it. I'm not totally sure where to begin diagnosing, but nslookups fail with "DNS request timed out. Timeout was 2 seconds. Server: unknown, Address: 192.168.1.111"
The address is the right one, but obviously the rest isn't working. Any help would really be appreciated.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
It does seem that way but I can't spot anything obvious that points to what the issue might be. The gateway and IPs look fine, the DNS server is correct. Settings are the same as on my laptop, which is running the same version of Windows 10 (albeit on a different WiFi card).
I've tried disabling IPV6 in the network adaptor (albeit it's off on the router anyway) and forcing it to the right DNS server but those don't seem to rectify it.
Details on ipconfig and nslookups below:
nslookup pi.hole
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.111
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
nslookup flurry.com 192.168.1.111
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.111
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
If you manually set the pc to a public DNS server (8.8.8.8), do you see the same issues? How close is the pc to the router? Can you connect to it with an Ethernet cable?
The nslookup output demonstrates that the request doesn't make it to Pi-hole, or the Server would read pi.hole.
With that output, I'd expect that you would not find A and AAAA lookups for flurry.com from your Win10 client if you check your Pi-hole's Query Log for it.
If this would happen for all clients alike, that would have suggested a firewall issue on your Pi-hole host machine.
As it is limited to just one client, it makes local interference on that device likely.
You wouldn't run any local firewall or antivirus package on that Windows client, e.g. AVG Secure DNS or AVAST Real-Site?
You'd have to disable those features in your antivirus package to have Pi-hole do its filtering.
I had tried it with 8.8.8.8 and 8.8.4.4 but neither seemed to resolve it. I snagged a 10m ethernet cable, what would I be looking for in connecting it directly?
I'll check the Query Log when I'm home and confirm, but it is odd that the issue is intermittent. At times it does connect, with the connection speed fluctuating wildly minute to minute. I've tried hotspotting from my phone and that connects fine, with stable speeds.
I only have Windows Defender, which would be the case on my laptop as well. I did try disabling its firewall (across all connections, and tried switching mine from private to public and back) but that seemed to make little difference too.