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

#1

Post by poitrus » Fri, Nov 22, 2019, 9:40 PM UTC

NextDNS first to block ALL third-party trackers disguised as first-party
medium.com

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

#2

Post by delfinom » Sun, Nov 24, 2019, 5:19 AM UTC

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

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

#3

Post by poitrus » Sun, Nov 24, 2019, 6:45 PM UTC

delfinom wrote: post #2

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

Source?

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

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

#4

Post by t3f » Mon, Nov 25, 2019, 2:03 AM UTC

poitrus wrote: post #3

delfinom wrote: post #2

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

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

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...

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

#5

Post by yegor » Tue, Nov 26, 2019, 4:13 PM UTC

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