Tpc.googlesyndication.com and googleads.g.doubleclick.net getting through

Help
2

A few thoughts:

  1. You are using block lists that are questionable.
https://dbl.oisd.nl/
https://dbl.oisd.nl/light/

The list maintainer selectively whitelists domains and does not publicize the domains they choose to whitelist. Domains that you would expect to be blocked are not always blocked. I would ditch these lists and select from more reputable lists here: https://wally3k.github.io

  1. Of the two questionable blocklists, only the second one is enabled. Let's check that list to see if it contains the two domains; and find it does.
pihole -q tpc.googlesyndication.com
 Match found in https://dbl.oisd.nl/light/:
   tpc.googlesyndication.com 
   tpc.googlesyndication.com.proxy.c9w.net

pihole -q googleads.g.doubleclick.net
Match found in **https://dbl.oisd.nl/light/** :
googleads.g.doubleclick.net
  1. The regex you have crafted are incorrect:

You have .*googlesyndication.* , which does not block tpc.googlesyndication.com

Add googlesyndication.com as a wildcard blacklist entry, and Pi-hole will convert that to the following regex which does block that domain.

(\.|^)googlesyndication\.com$

  1. If the browser you are using is able to load these domains, then the DNS queries for that browser are not going to Pi-hole. This can be caused by a few things:

  • The browser is using a DNS other than the DNS provided by the client OS (i.e. DNS over HTTPS).

  • The client is not using Pi-hole for DNS resolution.

From the client command prompt or terminal (and not via ssh into the Pi terminal), what are the outputs of the following:

nslookup pi.hole

nslookup tpc.googlesyndication.com 192.168.178.13