Windows 10 - Not receiving queries

Help
1

Expected Behaviour:

[Trying to get pihole to work one Windows 10]

Actual Behaviour:

[pihole is running and I can see the dashboard. There are only a tiny amount of queries going there. I have tried this multiple times using docker and wsl.]

Debug Token:

[https://tricorder.pi-hole.net/0seqFgWs/]

2

A few items noted:

You aren't running our shipped code (likely unrelated to this problem):

*** [ DIAGNOSING ]: Web version
[✓] Version: v5.20.1
[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)
             origin	https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.20.1-0-g3a11976-dirty
[i] Status:  M settings.php
[i] Diff: diff --git a/settings.php b/settings.php
          index 6ad968d..b799c9f 100644
          --- a/settings.php
          +++ b/settings.php
          @@ -213,7 +213,7 @@ if (isset($_GET['tab']) && in_array($_GET['tab'], array('sysadmin', 'dns', 'piho
                               <a href="#dns" aria-controls="dns" aria-expanded="<?php echo $tab === 'dns' ? 'true' : 'false'; ?>" role="tab" data-toggle="tab">DNS</a>
                           </li>
                           <li role="presentation"<?php if ($tab === 'piholedhcp') { ?> class="active"<?php } ?>>
          -                    <a href="#piholedhcp" aria-controls="piholedhcp" aria-expanded="<?php echo $tab === 'piholedhcp' ? 'true' : 'false'; ?>" role="tab" data-toggle="tab">DHCP</a>
          +                    <!--a href="#piholedhcp" aria-controls="piholedhcp" aria-expanded="<?php echo $tab === 'piholedhcp' ? 'true' : 'false'; ?>" role="tab" data-toggle="tab">DHCP</a-->
                           </li>
                           <li role="presentation"<?php if ($tab === 'web') { ?> class="active"<?php } ?>>
                               <a href="#web" aria-controls="web" aria-expanded="<?php echo $tab === 'web' ? 'true' : 'false'; ?>" role="tab" data-toggle="tab">Web interface</a>

No DHCP server answered during the DHCP-discover process, so the debug log doesn't show how your DNS is configured in the DHCP server.

From a client that you believe should be connected to the Pi-Hole for DNS (the Windows 10 client in this case), from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

nslookup flurry.com

nslookup flurry.com 192.168.0.50

3

Thank you for the reply! From my Windows PowerShell in admin mode.

PS C:\WINDOWS\system32> nslookup pi.hole
Server:  cdns01.comcast.net
Address:  2001:558:feed::1

*** cdns01.comcast.net can't find pi.hole: Non-existent domain

PS C:\WINDOWS\system32> nslookup flurry.com
Server:  cdns01.comcast.net
Address:  2001:558:feed::1

Non-authoritative answer:
Name:    flurry.com
Addresses:  34.225.127.72
          212.82.100.150
          54.161.105.65
          98.136.103.23
          74.6.136.150


PS C:\WINDOWS\system32> nslookup flurry.com 192.168.0.50
Server:  UnKnown
Address:  192.168.0.50

Name:    flurry.com
Addresses:  ::
          0.0.0.0
4

My current installation I did using this method: GitHub - DesktopECHO/Pi-Hole-for-WSL1: Ad-blocking DNS server for Windows • Unbound pre-configured • Deployment ready in minutes • Does not require hypervisor/docker

5

image

6

Your Comcast IPv6 DNS is answering. As a first troubleshooting step, disable IPv6 on the router and the Windows client and try these commands again.

Note in the third command that when you specifically direct the query to Pi-hole, Pi-hole answers properly.

This indicates the problem is not within Pi-hole.

7

I disabled DHCP server for IPV 6 in my router and applied. Results are the same:

PS C:\WINDOWS\system32> nslookup pi.hole
Server:  cdns01.comcast.net
Address:  2001:558:feed::1

*** cdns01.comcast.net can't find pi.hole: Non-existent domain
PS C:\WINDOWS\system32> nslookup flurry.com
Server:  cdns01.comcast.net
Address:  2001:558:feed::1

Non-authoritative answer:
Name:    flurry.com
Addresses:  34.225.127.72
          74.6.136.150
          54.161.105.65
          98.136.103.23
          212.82.100.150

PS C:\WINDOWS\system32> nslookup flurry.com 192.168.0.50
Server:  UnKnown
Address:  192.168.0.50

Name:    flurry.com
Addresses:  ::
          0.0.0.0

image

8

What changes did you make on the Windows 10 client?

9

Since your last message? None. I just changed the router.

In total? No idea. I first followed a tutorial of installing Docker (which required a ton of messing around to get Hyper-V working) and pihole through that. Then I uninstalled all of that and Hyper-V and tried the new method using WSL.

I definitely could have messed something up along the way, but I don't know what.

10

I'm sorry, I missed that I was supposed to disable IPV6 on my client as well. Did so and here are my results:

PS C:\WINDOWS\system32> nslookup pi.hole
Server: UnKnown
Address: 192.168.0.50

*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for pi.hole
PS C:\WINDOWS\system32> nslookup flurry.com
Server: UnKnown
Address: 192.168.0.50

Name: flurry.com
Addresses: ::
0.0.0.0

PS C:\WINDOWS\system32> nslookup flurry.com 192.168.0.50
Server: UnKnown
Address: 192.168.0.50

Name: flurry.com
Addresses: ::
0.0.0.0

11

Most of the internet seems to no longer work for me, either.

12

I've re-enabled IPV6. During that time it was off it does look like a lot of queries were going to pihole, but no websites were loading. I was still able to reply here though.

image

13

Any further insight on this? I'm willing to put the effort into testing and figuring it out, but I'm not sure where to investigate next. Thanks!

14

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.