HostlistsRegistry VS cname-trackers

request it? https://github.com/AdguardTeam/HostlistsRegistry

adguard dns 2.0 https://adguard-dns.com/

The domain of the website is adguard-dns.io. We did want to have the website on adguard-dns.com too but thanks to Google's shadow ban and the fact that they do not have any support we had to make a decision to use .io after all.

Which might require a major redesign. I'm guessing the niche between "yeah I'll just host my own pihole/adguard home" and "meh I'd just use the existing list" is too small to develop the feature. Competitors like controld don't allow any custom list, while AdGuard Private DNS uses a submission procedure.

You can suggest them here: GitHub

In the future, they will also plan to allow you to create your own private DNS server too if you are interested: https://adguard-dns.com (Beta)

We may simply add them to the list of available blocklists. If you want some list to be added, please request it here: https://github.com/AdguardTeam/HostlistsRegistry

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