[blacklisted domains shoud never go through]
[some blacklisted domains sometimes get through]
forgive me for my first topic post.
So my pi-hole isn't blocking 100% of the addresses of the blocklist 100% of the time. adservice.google.com sometimes gets through and sometimes gets blocked.
how to remediate?
[d906t0xqde]
There are specific ads that are injected via html5/javascript/ajax that Pi-hole does not block since it's not a content filter.
Pi-hole blocks (if the ad domain is listed in the ad block list) at DNS level, it never looks inside the page's content and does not strip anything.
If the ad delivery method is a non standard (hosted on a known ad delivery domain) and it's inserted via an obfuscated code (that again, does not translate into a DNS query) then Pi-hole will not block it.
You can look and see what google domains are blocked by tailing the log (from the Pi-hole admin interface) or run a query adlist for a specific domain.
So, I've setup pi-hole to be the dns server on my network. I have bind9 on the router and it is setup to send all network dns requests to the pi-hole. The machine used as the router only has one dns nameserver setup and that is the pi-hole, made sure 100% there is no other. My dns queries are going through the pihole some ads are blocked.
However
Despite having over 300k domains on blocklist and putting it in my blacklist as wildcard and exact match, adservice.google.com stll gets through and it's not the only one. I took a look at the query log and I saw that sometimes it's blocked sometimes it's not. I want it always blocked
ipv6 has been disabled
I used to have roughly the same 300k blocklist in bind9 on the router, it was slow but it never allowed anything through like pihole is doing.
please help
not really an acceptable answer when I know other dns based adblockers do the trick. please read the post I wrote after yours.
apologies I am new to discourse and had no clue how to correctly post my problem. will retry in the correct fashion.
My initial reply was based solely on the title of your initial post and nothing else.
Please upload a debug token by running pihole -d so that the devs can take a look and see if they spot anything.
what's the output of
dig adservice.google.com on your ubuntu ?
Also, in the query log, on the admin page, does it show as an AAAA query ?
output of "$ dig adservice.google.com" on the Ubuntu running pi-hole
; <<>> DiG 9.10.3-P4-Ubuntu <<>> adservice.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17440
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;adservice.google.com. IN A
;; ANSWER SECTION:
adservice.google.com. 2 IN A 10.5.5.53
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 01 21:56:11 EDT 2018
;; MSG SIZE rcvd: 65
output of "$ dig adservice.google.com" on Ubuntu client of pihole
; <<>> DiG 9.10.3-P4-Ubuntu <<>> adservice.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31728
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;adservice.google.com. IN A
;; ANSWER SECTION:
adservice.google.com. 2 IN A 10.5.5.53
;; Query time: 0 msec
;; SERVER: 10.5.5.53#53(10.5.5.53)
;; WHEN: Tue May 01 22:21:57 EDT 2018
;; MSG SIZE rcvd: 65
No visible problem there, the pi-hole is on the 10.5.5.53 address and the pi-hole is referencing it back to itself, as it should. No matter how many times I run ccleaner and "ipconfig /flushdns" on client machines I still see adservice.google.com coming through though.
no indication of any AAAA queries in the query log
new debug token is ve2gguodm5
This query resolved the host, to your device running pi-hole (internal IP).
That means that the query was intercepted and Pi-holed.
Looking at your debug token and the above command, everything looks like it’s working as it’s supposed to.
Can you upload (when it happens) an actual screenshot of the query log where the query was allowed?
And if possible, uplod a debug token when it happens. Maybe something else is failing there.
will do. thanks for the prompt response
here, it did it again, it's not green lighting it anymore in the query but it's still letting it through. I'll still be keeping an eye for when it greens it again
new token is oq2talmw2e
Your uBlock origin shows you the request being placed. That request is hard coded in the page(s) you visit and it will always show there as being “logged”.
Your pi-hole query log shows you the status of that request. Pi-holed.
Blocked. So it did it’s job.
To further test the Pi-hole blocking it, try opening that link directly. As in go to adservice.google.com
You should be prompted with the pi-hole splash/info page.
Ok, Guess it's doing the job. Thanks for your help.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
