NextDNS first to block ALL third-party trackers disguised as first-party

Posted by poitrus on Friday November 22, 2019 @04:40PM
from the medium.com dept.

https://medium.com/nextdns/nextdns-added-cname-uncloaking-support-becomes-the-first-cross-platform-solution-to-the-problem-e3f437f84342

( 4 comments | 21 points | on HN )

Re:NextDNS first to block ALL third-party trackers disguised... by yegor on Tuesday November 26, 2019 @11:13AM (#21639540)

Neat, but Windscribe ROBERT already supported this for over a year: https://windscribe.com/features/robert

[ Parent | on HN ]

Re:NextDNS first to block ALL third-party trackers disguised... by delfinom on Sunday November 24, 2019 @12:19AM (#21618543)

Late to the party. Trackers are now moving to A records instead of just CNAMES just because blockers were already emerging.

[ Parent | on HN ]

Re:NextDNS first to block ALL third-party trackers disguised... by poitrus on Sunday November 24, 2019 @01:45PM (#21622373)

Source?

A records are blockable the same way, it wouldn’t buy them anything here.

[ Parent | on HN ]

Re:NextDNS first to block ALL third-party trackers disguised... by t3f on Sunday November 24, 2019 @09:03PM (#21624898)

If it is true it would buy ad servers greater obfuscation since blockers were relying on CNAME metadata to differentiate between safe and unsafe targets. If more reverse lookup and secondary metadata and vhost dereferencing is required it will complicate performant ad stripping at a minimum.

[0] https://discourse.pi-hole.net/t/apply-pi-hole-blocking-to-cn...

[1] https://github.com/uBlockOrigin/uBlock-issues/issues/780#iss...

[ Parent | on HN ]