Re:Cname / DNS based third party tracking
by andrenotgiant on Sunday February 28, 2021 @09:04PM
(#26298979)
IPV6 also greatly complicates IP-based blocking. There are so many IPV6 addresses that it'd be relatively cheap for an ad tracker to develop a system that uses a new one every day.
[ Parent
| on HN ]
Re:Cname / DNS based third party tracking
by half-kh-hacker on Monday March 01, 2021 @12:08AM
(#26299926)
If you get allocated a /32, you have 95 bits of addresses to play with. You could use a different IP every millisecond and not have problems.
Re:Cname / DNS based third party tracking
by deadlyllama on Monday March 01, 2021 @01:35AM
(#26300248)
Yeah, but they'd all be in the same /32, which is trivial to block. You'd have to intersperse "legitimate" users through your space to thwart that.
What would be wrong with blocking the entire /32 if you know the owner of it is using it in such a way?
Re:Cname / DNS based third party tracking
by citrin_ru on Monday March 01, 2021 @04:26AM
(#26301004)
Ad trackers often use some ISP or cloud provider with many other customers. Which network ISP assigned to a given customer is not public information. Even if a company has own AS, blocking it not always an option: Google, Oracle, IBM and others potentially can use any IP in their networks for Ads, but too big to block.