A quick log check Pls

pilothobs · November 17, 2022, 8:51pm

Hello All.

It's been a while. I have missed Pi-Hole and just set it up again. This time I am using docker on a server instead of a Pi.

The issue I am facing: It shows that it is working correctly but my ads are not being blocked

Details about my system: Docker on server

What I have changed since installing Pi-hole: nothing.

I have pointed the DNS in the router to the pi-hole IP address(no others were entered)
Also, when I use nslookup it returns 127.0.0.53 not the 192.168.1.58 its on.

https://tricorder.pi-hole.net/tv2QyCbT/

Thanks for your help

Hobs

Bucking_Horn · November 17, 2022, 9:05pm

Your debug log shows your Pi-hole to be receiving and blocking queries as expected:

   [2022-11-17 19:32:40.285 1280M] Imported 1050 queries from the long-term database
   [2022-11-17 19:32:40.285 1280M]  -> Total DNS queries: 1050
   [2022-11-17 19:32:40.285 1280M]  -> Cached DNS queries: 56
   [2022-11-17 19:32:40.285 1280M]  -> Forwarded DNS queries: 547
   [2022-11-17 19:32:40.285 1280M]  -> Blocked DNS queries: 447
   [2022-11-17 19:32:40.285 1280M]  -> Unknown DNS queries: 0
   [2022-11-17 19:32:40.285 1280M]  -> Unique domains: 381
   [2022-11-17 19:32:40.285 1280M]  -> Unique clients: 2
   [2022-11-17 19:32:40.285 1280M]  -> Known forward destinations: 1

How did you configure your router to make use of Pi-hole?
As local DNS server via DHCP?
It may take a while for DHCP clients to pck up their new DNS server from your router, when they renew their DHCP lease.

Likely unrelated, but your debug log suggests you didn't set FTLCONF_LOCAL_IPV4 for your Pi-hole Docker container?

pilothobs · November 17, 2022, 10:24pm

Hello Bucking_Horn

Thanks for the reply.
I pointed the router to pi-holes IP address in DHCP
Do I set the FTLCONF_LOCAL_IPV4 to my routers IP? Also, Do I have to set the DNS in Network to the IP of pi-hole?

TIA

Hobs

pilothobs · November 18, 2022, 9:29pm

I'm Still getting ads....

Bucking_Horn · November 18, 2022, 9:41pm

Usually, you'd set FTLCONF_LOCAL_IPV4 to your Pi-hole host's private range IP address. It may only impact accessing PI-hole's web UI, not it's DNS filtering.

Run from a client that you expect to use Pi-hole for DNS, what's the output of:

nslookup pi.hole

nslookup flurry.com

pilothobs · November 18, 2022, 9:57pm

Hey

Idk. I found some guides that had you build a network. I followed them and now it won't load. Is that even necessary?
I also tried(first) to just put in the the FTLCONF_LOCAL_IPV4 address and was still getting ads.

Pretty burnt out. I've been messing with it for 2 days

TIA

Hobs

pilothobs · November 20, 2022, 2:22am

Here is the output.

Hobs

Screenshot from 2022-11-19 21-21-31

rdwebdesign · November 20, 2022, 3:06am

Just a note:
When you post command line output is preferable to use text instead of images.
Text is searchable and easier to copy and paste if needed.

pilothobs · November 20, 2022, 8:31pm

sorry

pilothobs@NUC-8i:~$ nslookup pi.hole
Server:		127.0.0.53
Address:	127.0.0.53#53

** server can't find pi.hole: NXDOMAIN

pilothobs@NUC-8i:~$ nslookup flurry.com
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	flurry.com
Address: 212.82.100.150
Name:	flurry.com
Address: 74.6.136.150
Name:	flurry.com
Address: 98.136.103.23

I'm still getting ads. I'm pretty sure that pihole is not talking to the router. When I enter the router's IP address range in pihole DHCP it says those addresses are not available. When I enter the range from the virtual ethernet adapter. It works.
here is what it looks like over on the server....

Microsoft Windows [Version 10.0.19044.2251]
(c) Microsoft Corporation. All rights reserved.

C:\Users\skira>ipconfig

Windows IP Configuration


Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Intel Ethernet I210 #2:

   Connection-specific DNS Suffix  . : localdomain
   Link-local IPv6 Address . . . . . : fe80::2931:cb97:8437:40a3%13
   IPv4 Address. . . . . . . . . . . : 192.168.1.240
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::caa9:4d2d:7391:e0ef%30
   IPv4 Address. . . . . . . . . . . : 172.18.144.1
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :

C:\Users\skira>nslookup pi.hole
Server:  ubnt
Address:  192.168.1.1

*** ubnt can't find pi.hole: Non-existent domain

C:\Users\skira>nslookup flurry.com
Server:  ubnt
Address:  192.168.1.1

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

C:\Users\skira>

Bucking_Horn · November 21, 2022, 5:26pm

Your nslookup results show that the machine you run those from doesn't use Pi-hole for DNS, but rather a local stub resolver at 127.0.0.53.
That stub resolver also doesn't forward DNS requests to Pi-hole upstream, or else it would have returned your Pi-hole's IP instead of NXDOMAIN.

But judging by your prompt (pilothobs@NUC-8i), it would seem you ran those nslookups from your Pi-hole host, when I asked you to run them from a client.

If that's indeed your Pi-hole host, then its DNS resolution would be irrelevant for Pi-hole's DNS operation. It would be ok and can even be of advantage that Pi-hole's host would be using a public DNS server.

Now let's take a look at your Windows client, which you've now also provided results for:

Your Windows nslookup results show that your Windows client is using your machine at 192.168.1.1 for DNS (your router, presumably), which in turn did not use Pi-hole as upstream, as obvious by that NXDOMAIN.

You should verify your router settings again.

Make sure you did configure your router to distribute your Pi-hole host machine's IPv4 via DHCP, and also check the lease validity - routers may hand out DHCP leases valid for days.

pilothobs · November 29, 2022, 3:43pm

Here's from a client.

Here are the lates logs and info.

pilothobs@NUC-8i:~$ nslookup pi.hole
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: pi.hole
Address: 192.168.1.240
Name: pi.hole
Address: fe80::9c7e:3400:d144:77b2

And for flurry.compilothobs@NUC-8i:~$ nslookup flurry.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
Address: ::

Here is the link to the logs

https://tricorder.pi-hole.net/HIDT2fX7/

The problem is that pihole is working but not blocking everything. I still get random ads. and when I use a checker about half are blocked.

Here is the checker.

TIA and I hope you had a good Turkey day.

Hobs

Bucking_Horn · December 1, 2022, 10:36am

(I have no idea what a Turkey day is.)

Run from your Windows client, what is the output of:

netsh interface ipv6 show dnsservers

pilothobs · December 1, 2022, 1:50pm

Ha-ha. That's funny. I guess I shouldn't assume everyone is an American. I don't have a windows client. I was running windows 10 on the server and I dumped it and installed Ubuntu.

Hobs

system · December 22, 2022, 5:56pm

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