Running pihole/pihole:latest on Pi3 via docker sha256:623d099087d50c273380002b221f7c5e6691fb603bafbea949bc1e72857d1ed0
Was an upgrade of a previous version of the container. Noticed that ads appear to be getting through, checked blacklist, ran a gravity upgrade, still nothing. Did some querying here and had a hard time getting through all of the posts where people had resolvers set correctly. I by-passed client configuration (to be sure) and checked resolving directly via dig:
$ dig @pi.hole taboola.com
; <<>> DiG 9.11.5-P4-5.1ubuntu2.1-Ubuntu <<>> @pi.hole taboola.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22791
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;taboola.com. IN A
;; ANSWER SECTION:
taboola.com. 148 IN A 151.101.193.181
taboola.com. 148 IN A 151.101.1.181
taboola.com. 148 IN A 151.101.129.181
taboola.com. 148 IN A 151.101.65.181
;; Query time: 24 msec
;; SERVER: 10.10.0.30#53(10.10.0.30)
;; WHEN: Sun Apr 12 16:50:15 PDT 2020
;; MSG SIZE rcvd: 148
Based on a comment in a different thread, I tried blowing away the FTL Database and restarting the container, but that doesn't appear to work.
Expected Behaviour:
Ad Blocking
Actual Behaviour:
No Blocking
