block ads
new instal in docker, pihole with static ip,replaced the dns on router and still no ads are blocked.tried many compination (manual add in all the pcs the pihole ip ,but nothing changed) 0.3% percent block ,
tried also to put some blacklist lists with no success .
2 days now reading post on internet to find a solution with no luck can anyone help please?
Your debug log shows the following activity in the past 24 hours - queries from 14 unique clients.
[2019-11-15 13:27:21.630 25528] Imported 23964 queries from the long-term database
[2019-11-15 13:27:21.631 25528] -> Total DNS queries: 23964
[2019-11-15 13:27:21.631 25528] -> Cached DNS queries: 21883
[2019-11-15 13:27:21.631 25528] -> Forwarded DNS queries: 1400
[2019-11-15 13:27:21.631 25528] -> Exactly blocked DNS queries: 271
[2019-11-15 13:27:21.631 25528] -> Unknown DNS queries: 410
[2019-11-15 13:27:21.631 25528] -> Unique domains: 388
[2019-11-15 13:27:21.631 25528] -> Unique clients: 14
[2019-11-15 13:27:21.631 25528] -> Known forward destinations: 2
Run these commands to see which domains are being queried and blocked:
echo ">top-clients withzero (15)" | nc localhost 4711
echo ">top-domains" | nc localhost 4711
echo ">top-ads" | nc localhost 4711
thank you for your reply. i add some lists on blacklist in the morning ,dont know if that matters...
type or paste code here
$ sudo service dnsmasq status
Unit dnsmasq.service could not be found.
pi@raspberrypi:~ $ tail /var/log/pihole.log
Nov 15 11:04:12 dnsmasq[1014]: cached 8.8.8.8 is dns.google
Nov 15 11:04:12 dnsmasq[1014]: query[PTR] 4.4.8.8.in-addr.arpa from 127.0.0.1
Nov 15 11:04:12 dnsmasq[1014]: cached 8.8.4.4 is dns.google
Nov 15 11:04:12 dnsmasq[1014]: query[PTR] 1.1.1.1.in-addr.arpa from 127.0.0.1
Nov 15 11:04:12 dnsmasq[1014]: cached 1.1.1.1 is one.one.one.one
Nov 15 11:04:12 dnsmasq[1014]: query[PTR] 8.2.168.192.in-addr.arpa from 127.0.0.1
Nov 15 11:04:12 dnsmasq[1014]: DHCP 192.168.2.8 is DESKTOP-PK0BA65.lan
Nov 15 11:04:12 dnsmasq[1014]: query[PTR] 11.2.168.192.in-addr.arpa from 127.0.0.1
Nov 15 11:04:12 dnsmasq[1014]: DHCP 192.168.2.11 is office.lan
Nov 15 11:04:13 dnsmasq[1014]: exiting on receipt of SIGTERM
pi@raspberrypi:~ $ sudo service dnsmasq status
Unit dnsmasq.service could not be found.
pi@raspberrypi:~ $ echo ">top-clients withzero (15)" | nc localhost 4711
0 6276 127.0.0.1 localhost
1 885 192.168.2.14 192.168.2.14
2 765 192.168.2.7 192.168.2.7
3 120 192.168.2.5 192.168.2.5
4 79 192.168.2.12 192.168.2.12
5 72 192.168.2.10 192.168.2.10
6 47 192.168.2.13 192.168.2.13
7 38 192.168.2.20 192.168.2.20
8 28 192.168.2.23 192.168.2.23
9 19 192.168.2.8 192.168.2.8
10 9 192.168.2.2 192.168.2.2
11 7 192.168.2.15 192.168.2.15
12 7 192.168.2.6 192.168.2.6
13 4 192.168.2.3 192.168.2.3
14 4 192.168.2.4 192.168.2.4
---EOM---
echo ">top-domains" | nc localhost 4711
echo ">top-ads" | nc localhost 4711
i just spoke with my internet provider to disable ip6v (not available in my country ) cause i couldnt do it from my interface.
You shouldn't have a dnsmasq service running, since dnsmasq is embedded in pihole-FTL and pihole-FTL should be the running process.
sudo service pihole-FTL status
i dont know what this is:innocent: but here is the reply !
pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Fri 2019-11-15 13:38:33 EET; 5h 35min ago
Docs: man:systemd-sysv-generator(8)
Process: 25814 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 25840 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 0B
CPU: 0
CGroup: /system.slice/pihole-FTL.service
Νοέ 15 13:38:33 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Νοέ 15 13:38:33 raspberrypi pihole-FTL[25840]: Not running
Νοέ 15 13:38:33 raspberrypi pihole-FTL[25840]: pihole-FTL is already running
Νοέ 15 13:38:33 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
What were the outputs of these commands? I didn't see them posted.
echo ">top-domains" | nc localhost 4711
echo ">top-ads" | nc localhost 4711
here they are !
echo ">top-domains" | nc localhost 4711
0 478 14.2.168.192.in-addr.arpa
1 478 4.4.8.8.in-addr.arpa
2 478 11.2.168.192.in-addr.arpa
3 472 8.2.168.192.in-addr.arpa
4 465 1.2.168.192.in-addr.arpa
5 465 1.1.1.1.in-addr.arpa
6 451 de.processor.smartcamera.api.io.mi.com
7 445 de.business.smartcamera.api.io.mi.com
8 351 23.2.168.192.in-addr.arpa
9 338 34.2.168.192.in-addr.arpa
0 19 onesignal.com
1 18 googleads.g.doubleclick.net
2 16 www.google-analytics.com
3 14 geo.yahoo.com
4 13 v10.events.data.microsoft.com
5 9 www.googleadservices.com
6 9 csc.beap.bc.yahoo.com
7 9 sb.scorecardresearch.com
8 8 beap.gemini.yahoo.com
9 6 bs.serving-sys.com
---EOM---
As shown in you last output, some ad domains are being blocked (or at least have been blocked in the past 24 hours).
From a connected client where you are seeing ads, what are the outputs of the following commands:
nslookup pi.hole
nslookup flurry.com
Server: a0d7b954-pi-hole
Address: 192.168.2.111
Name: pi.hole
Address: 192.168.2.111
Server: a0d7b954-pi-hole
Address: 192.168.2.111
Name: flurry.com
Addresses: ::
0.0.0.0```Those are the expected replies. Pi-Hole is the DNS server, and the correct reply for the flurry.com domain (contained on several of the default block lists) is 0.0.0.0.
Can you provide an example of a website where you are seeing ads? URL, screen shots, etc.
i make a restart on the router, i add static ips on all by hand, i set the secondary dns to 0.0.0.0 ,clear cache and the percent went to 3.8% .
these are from yahoo from my mobile skip advertising.
Screenshot_20191115-194129_Chrome|230x500
When you tail the pihole log and reload that page on that client, are you seeing the DNS traffic going through Pi-Hole?
yes.
maybe i should add some more black lists ?
Not necessarily. Use these tools to determine the source of the ads:
thank you for you time and your replys , for the moment i will leave it as it is .im newby on the linux/raspberry and all these are over my knowledge !
again, thank you for your time !
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
