Pi-hole querie/network queries empty

[meerweten]

Please follow the below template, it will help us to help you!

Expected Behaviour:

dns requests available in querie list making it possible to block them with the button

Actual Behaviour:

querry list is empty

Debug Token:

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

note:
tail on piole.log revels many items
tail on pihole-ftl is empty
blocking is working

setupvars:

DNSMASQ_LISTENING=single
PIHOLE_DNS_3=2001:4860:4860:0:0:0:0:8888
PIHOLE_DNS_4=2001:4860:4860:0:0:0:0:8844
PIHOLE_DNS_5=192.168.0.1#53
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
CONDITIONAL_FORWARDING=false
WEBPASSWORD=285960c0f1fa143c4b2d5d9ce89d7ebae3a5b1c4d8ccbf837849c9d2cde82e7f
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.2/24
IPV6_ADDRESS=2a02:1812:2c26:2d00:cdb1:d795:36ee:b07d
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
BLOCKING_ENABLED=true

pihole-FTL.conf:
PRIVACYLEVEL=0

[Comedy]

Hi, On your windows machine can you check what DNS server you are using. It looks like your Pi Hole is on 192.168.0.2 but the chances are your router is still providing the DNS server of itself (most likely 192.168.0.1) to devices when they connect.

You can check by opening cmd and typing:

ipconfig /all | findstr DNS

Mine for example shows 10.0.0.6:

C:\Users>ipconfig /all | findstr DNS
   DNS Suffix Search List. . . . . . : lan
   Connection-specific DNS Suffix  . : lan
   DNS Servers . . . . . . . . . . . : 10.0.0.6
   Connection-specific DNS Suffix  . :

If you still see 192.168.0.1 then you need to change the settings of your router to provide your Pi Hole ip of 192.168.0.2 as your DNS server, this will vary depending on the router. You are also able to use Pi Hole as your DHCP server if your router does not allow changing DNS server.

How do I use Pi-hole's built in DHCP server (and why would I want to)?

Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page, which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. …

[deHakkelaar]

Any data for 192.168.0.3 in the database if run below one ?

sqlite3 /etc/pihole/pihole-FTL.db 'SELECT * FROM queries WHERE client="192.168.0.3"'

If data in dbase but none displayed on web, check live logs when querying via the web:

sudo tailf /var/log/lighttpd/access.log

sudo tailf /var/log/lighttpd/error.log

The web part depends on below PHP modules to be installed (versions might differ for your distro):

pi@noads:~ $ apt policy php7.0-json
php7.0-json:
  Installed: 7.0.33-0+deb9u3
[..]

---

pi@noads:~ $ apt policy php7.0-sqlite3
php7.0-sqlite3:
  Installed: 7.0.33-0+deb9u3
[..]