Web interface showing zero queries


#1

Expected Behaviour:

I should see a number greater than zero in the web interface for Total queries and Queries blocked. I should see something showing up in the query log

Actual Behaviour:

The web interface is reporting zero for Total queries and Queries blocked. The query log is empty. My pi-hole installation does seem to be working though. I initially installed the current v3.3.0 (?) but had to revert to v3.2.1 because dnsmasq wasn’t working on my system.

Debug Token:

e29nfp5145


#2

What’s the output of

systemctl is-active dnsmasq

or

service dnsmasq status

#3
$ sudo service dnsmasq status
 * Checking DNS forwarder and DHCP server dnsmasq
 * (running)

#4

Can you try flushing your browser cache?


#5

I’ve flushed the cache and nothing has changed


#6

Can you send your FTL log?

cat /var/log/pihole-FTL.log | pihole tricorder

#7

xxjuqc7agf


#8
[2018-04-08 03:09:11.604]  -> Total DNS queries: 0
[2018-04-08 03:09:11.604]  -> Cached DNS queries: 0
[2018-04-08 03:09:11.604]  -> Forwarded DNS queries: 0
[2018-04-08 03:09:11.604]  -> Exactly blocked DNS queries: 0
[2018-04-08 03:09:11.604]  -> Wildcard blocked DNS queries: 0
[2018-04-08 03:09:11.605]  -> Unknown DNS queries: 0
[2018-04-08 03:09:11.605]  -> Unique domains: 0
[2018-04-08 03:09:11.605]  -> Unique clients: 0
[2018-04-08 03:09:11.605]  -> Known forward destinations: 0

You don’t seem to have any clients connected to Pi-hole.


#9

Interesting.

All the devices on my network are configured to use my router (Unifi security gateway) for DNS forwarding, and the router is configured to use the pi-hole server for DNS. I have deliberately not configured any backup DNS servers and disabled all ad-blockers.

I am not currently seeing any ads on any websites and if I If I log into the server and disable dnsmasq (sudo service dnsmasq stop) I immediately lose all dns services. pi.hole/admin correctly resolves to the web interface.

I believe that this is all evidence I am connecting to the pi-hole correctly, but happy to be corrected. Is there anything else I can do to investigate this?


#10

When you run pihole -t, do you see queries from your clients?


#11

Here’s a brief 10 second sample from pihole -t. It seems very busy. It looks like there are some DNS queries from clients. There is also a huge amount of activity from the switch the server is connected to. Is that normal?

Anyway, I hope there is something useful in here.

Apr  9 21:11:58 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:11:58 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:11:58 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:11:58 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:11:58 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:11:58 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:11:59 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:11:59 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:11:59 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:11:59 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:11:59 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:11:59 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:11:59 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:11:59 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:00 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:00 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:00 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:00 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:00 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:00 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:00 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:00 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:00 dnsmasq[27039]: query[A] fonts.gstatic.com from 192.168.1.1
Apr  9 21:12:00 dnsmasq[27039]: forwarded fonts.gstatic.com to 1.0.0.1
Apr  9 21:12:00 dnsmasq[27039]: query[A] fonts.googleapis.com from 192.168.1.1
Apr  9 21:12:00 dnsmasq[27039]: forwarded fonts.googleapis.com to 1.0.0.1
Apr  9 21:12:00 dnsmasq[27039]: query[A] s.w.org from 192.168.1.1
Apr  9 21:12:00 dnsmasq[27039]: forwarded s.w.org to 1.0.0.1
Apr  9 21:12:00 dnsmasq[27039]: query[A] s0.wp.com from 192.168.1.1
Apr  9 21:12:00 dnsmasq[27039]: forwarded s0.wp.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] stats.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: /etc/pihole/gravity.list stats.wp.com is 192.168.1.100
Apr  9 21:12:01 dnsmasq[27039]: query[A] i1.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded i1.wp.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] i2.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded i2.wp.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: reply gstaticadssl.l.google.com is 216.58.220.99
Apr  9 21:12:01 dnsmasq[27039]: query[A] i0.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded i0.wp.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: reply s.w.org is 192.0.77.48
Apr  9 21:12:01 dnsmasq[27039]: reply s0.wp.com is 192.0.77.32
Apr  9 21:12:01 dnsmasq[27039]: reply googleadapis.l.google.com is 216.58.220.106
Apr  9 21:12:01 dnsmasq[27039]: query[A] 0.gravatar.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded 0.gravatar.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] 1.gravatar.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded 1.gravatar.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] 2.gravatar.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded 2.gravatar.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:01 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:01 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:01 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:01 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:01 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:01 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:01 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:01 dnsmasq[27039]: reply i1.wp.com is 192.0.77.2
Apr  9 21:12:01 dnsmasq[27039]: reply i2.wp.com is 192.0.77.2
Apr  9 21:12:01 dnsmasq[27039]: reply i0.wp.com is 192.0.77.2
Apr  9 21:12:01 dnsmasq[27039]: reply 0.gravatar.com is 192.0.73.2
Apr  9 21:12:01 dnsmasq[27039]: reply 2.gravatar.com is 192.0.73.2
Apr  9 21:12:01 dnsmasq[27039]: reply 1.gravatar.com is 192.0.73.2
Apr  9 21:12:01 dnsmasq[27039]: query[A] jetpack.wordpress.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded jetpack.wordpress.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] public-api.wordpress.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded public-api.wordpress.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] s1.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded s1.wp.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: reply s1.wp.com is 192.0.77.32
Apr  9 21:12:01 dnsmasq[27039]: reply jetpack.wordpress.com is 192.0.78.26
Apr  9 21:12:01 dnsmasq[27039]: reply jetpack.wordpress.com is 192.0.78.27
Apr  9 21:12:01 dnsmasq[27039]: reply public-api.wordpress.com is 192.0.78.22
Apr  9 21:12:01 dnsmasq[27039]: reply public-api.wordpress.com is 192.0.78.23
Apr  9 21:12:01 dnsmasq[27039]: query[A] s2.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded s2.wp.com to 1.0.0.1
Apr  9 21:12:01 dnsmasq[27039]: query[A] widgets.wp.com from 192.168.1.1
Apr  9 21:12:01 dnsmasq[27039]: forwarded widgets.wp.com to 1.0.0.1
Apr  9 21:12:02 dnsmasq[27039]: reply s2.wp.com is 192.0.77.32
Apr  9 21:12:02 dnsmasq[27039]: reply widgets.wp.com is 192.0.77.32
Apr  9 21:12:02 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:02 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:02 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:02 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:02 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:02 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:02 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:02 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:03 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:03 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:03 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:03 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:03 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:03 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:03 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:03 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:04 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:04 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:04 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:04 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:04 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:04 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:04 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:04 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:04 dnsmasq[27039]: query[A] e6858.dsce9.akamaiedge.net from 192.168.1.1
Apr  9 21:12:04 dnsmasq[27039]: forwarded e6858.dsce9.akamaiedge.net to 1.0.0.1
Apr  9 21:12:04 dnsmasq[27039]: query[AAAA] e6858.dsce9.akamaiedge.net from 192.168.1.1
Apr  9 21:12:04 dnsmasq[27039]: forwarded e6858.dsce9.akamaiedge.net to 1.0.0.1
Apr  9 21:12:05 dnsmasq[27039]: reply e6858.dsce9.akamaiedge.net is 23.37.130.181
Apr  9 21:12:05 dnsmasq[27039]: reply e6858.dsce9.akamaiedge.net is 2600:1415:10:185::1aca
Apr  9 21:12:05 dnsmasq[27039]: reply e6858.dsce9.akamaiedge.net is 2600:1415:10:18b::1aca
Apr  9 21:12:05 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:05 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:05 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:05 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:05 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:05 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:05 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:05 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:06 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:06 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:06 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:06 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:06 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:06 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:06 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:06 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:07 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:07 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:07 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:07 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:07 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:07 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:07 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:07 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4
Apr  9 21:12:08 dnsmasq[27039]: query[AAAA] eth0 from 192.168.1.105
Apr  9 21:12:08 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv6
Apr  9 21:12:08 dnsmasq[27039]: query[AAAA] eth0.localdomain from 192.168.1.105
Apr  9 21:12:08 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv6
Apr  9 21:12:08 dnsmasq[27039]: query[A] eth0 from 192.168.1.105
Apr  9 21:12:08 dnsmasq[27039]: cached eth0 is NXDOMAIN-IPv4
Apr  9 21:12:08 dnsmasq[27039]: query[A] eth0.localdomain from 192.168.1.105
Apr  9 21:12:08 dnsmasq[27039]: cached eth0.localdomain is NXDOMAIN-IPv4

#12

That shows Pi-hole is working so the problem must lie with FTL or the Web interface.


#13

OK. That’s good news I guess.

How would I go about identifying where the problem lies amongst those possibilities?


#14

Trying to solve this.

If I run pihole -c -j I get {"domains_being_blocked":121066,"dns_queries_today":0,"ads_blocked_today":0,"ads_percentage_today":0.000000}

Am I correct in interpreting this to mean that FTL is running, but incorrectly reporting no activity?

I also have run the following commands if they can help anyone help me;

~$ sudo service pihole-FTL status
status: Unknown job: pihole-FTL

~$ sudo service pihole-FTL restart

Stopped

rm: cannot remove ‘/var/run/pihole/FTL.sock’: No such file or directory
FTL started!

~$ ps ax | grep FTL
 3728 ?        Sl     0:03 /usr/bin/pihole-FTL

#15

Can you run through the FTL debugging process?


#16

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