cname-trackers VS pihole-regex

Note that CNAMEs is literally caused by GDPR, and the pathway every single ad or tracking company seems to go sooner or later.

For people not understanding how it works: you can set a CNAME entry on your tracker.domain.tld to bypass all Browser's third-party tracking preventions, and make it look like it's a normal subdomain of your website.

You need to make a CNAME tracker database manually by resolving the reverse entries for known IPs. Usually there is hundreds or thousands of CNAME entries pointing to the same IP address.

The AdGuard team also made a database for this, in case anyone needs it for UBOL [1]

[1] https://github.com/AdguardTeam/cname-trackers

So nextdns’s third party disguised trackers is actually really tiny of a list, like 30 domains. (Im trying to add more so it has the same amount of cname’s blocked as adguard). Anyways, the reason why the list is so tiny is because it uses wildcard logic so all subdomains get blocked. It already uses some of the cname companies that adguards cname-tracker list uses but not all. Hopefully my pull request can get merge eventually because then the setting will be a little bit more effective

I see fathom on Adguard CNAME tracker. Example:

> uBlock Origin already performs CNAME decloaking and blocks this approach, it’s pretty cool.

... which in return is a static list of domains which needs to be regularly updated, and therefore is not really failsafe. uBlock0 uses Adguard's scraped dataset [1] as a source to do this, as Chrome Extensions cannot make DNS requests without a DNS-via-HTTPS endpoint.

[1] https://github.com/AdguardTeam/cname-trackers

Not sure where I should report this, but I seem to have found a CNAME cloaking tracker which i don't find in either the original or disguised tracker lists here https://github.com/AdguardTeam/cname-trackers Is there a mechanism for reporting these? I saw someone posted a list on github, but no response there. Maybe this example is just ordinary tracking though?

Are you able to block trackers/ads using this new CNAME cloaking technique? https://github.com/AdguardTeam/cname-trackers

There are wrappers for updating regex lists that can be modified with other URLs. This was floating around for a while: https://github.com/mmotti/pihole-regex/blob/master/install.py and this is another method: https://www.bentasker.co.uk/posts/documentation/general/refreshing-piholes-regex-block-list-from-external-sources.html With enough regex tweaking I bet you could shave at least tens of thousands of lines off your list, and it could be divided into regex entries for domains where it makes sense, with the rest being non-regex domain entries. Simple regex that is functionally equivalent to AdBlock style wildcard blocks won't notably bog down the system either. It might take a few hours to get a workflow going to streamline producing such a list, but it can be done.

I also have a bunch of RegEx blacklisted from this pihole-regex/regex.list at master · mmotti/pihole-regex · GitHub and these:

Here's a list of domains I've used for years. All of which have been collected from different websites and sources such as https://firebog.net/ and https://github.com/mmotti/pihole-regex.

I also suggest these regex blocks

Your mileage may vary, but a combination of the default pi-hole list, the firebog.net lists (green, checkmark lists only), and the https://github.com/mmotti/pihole-regex/blob/master/regex.list do a pretty complete job for me.

While not perfect, and does not directly address the YouTube ads, I can suggest setting up mmotti's Regex Filters for Pi-hole.

I did also find these as well: https://github.com/mmotti/pihole-regex/blob/master/regex.list

Maybe this help: https://github.com/mmotti/pihole-regex