Admin page showing 0 queries blocked

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

Expected Behaviour:

domains on gravity list should be blocked

Actual Behaviour:

0 quries are blocked

Debug Token:

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

Welcome to the Pi-hole community, RadekG. :slight_smile:

Your debug log shows your Pi-hole has been successfully introduced into your network, with full IPv4 connectivty.
It is also positively receiving, processing and forwarding DNS queries, but not yet showing any DNS queries blocked.

This could be the case if Pi-hole didn't encounter anything to block so far.

Pi-hole does filter and block queries if a match is found:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] epom-sync.rutarget.ru is 0.0.0.0 via localhost (127.0.0.1)
[✓] epom-sync.rutarget.ru is 0.0.0.0 via Pi-hole (192.168.0.111)
[✓] doubleclick.com is 216.58.215.78 via a remote, public DNS server (8.8.8.8)

Would you have an example of a domain name that you expect to blocked when it isn't?

Also, some of your lists are not designed for Pi-hole.
It seems they do not conform to the hosts format, e.g.
(^|\.)adform\.net$
You should remove any lists with similar entries.

EDIT: It seems that this is the offending list:

https://raw.githubusercontent.com/MajkiIT/polish-ads-filter/master/polish-pihole-filters/hostfile.txt

contains:

# [Regex]
0.0.0.0 (^|\.)gemius\.(com|pl)$
0.0.0.0 (^|\.)doubleclick\.(com)$
0.0.0.0 (^|\.)adocean\.(pl)$
0.0.0.0 (^|\.)adform\.net$
0.0.0.0 (^|\.)adsbtrack\.com$
0.0.0.0 (^|\.)adserver\.snapads\.com$
0.0.0.0 (^|\.)audienceinsights\.net$
0.0.0.0 (^|\.)behavioralengine\.com$
0.0.0.0 (^|\.)clickmatic\.pl$
0.0.0.0 (^|\.)hit\.gemius\.pl$
0.0.0.0 (^|\.)hit\.interia\.pl$
0.0.0.0 (^|\.)lcx\.pl$
0.0.0.0 (^|\.)meetrics\.net$
0.0.0.0 (^|\.)smartadserver\.com$
0.0.0.0 (^|\.)mylead\.global$

You should remove it from Pi-hole's blocklists and contact that list's maintainer to alert him of these errors.

I fund problem :blush:

DHCP was pointing into wrong DNS it’s look like it was changed by mistake to default in last few days .

Sorry for trouble .

Radek

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