3 ms·
It's a problem of their own making that doesn't require a solution. After the client gets the IP address of the content web server from the DNS resolver, the c
by cnst 5y ago
It's a problem of their own making that doesn't require a solution.
After the client gets the IP address of the content web server from the DNS resolver, the client has to connect directly to the content web server, and the whole IP address — not just the subnet — is immediately shared with the content server anyways.
The market is supposed to regulate this abusive behaviour by showing how much slower the websites work when resolved through Cloudflare DNS compared to Google DNS or any other DNS providers that support EDNS Client Subnet. It seems that most of DNS benchmarks simply test how fast the names resolve, not how good of a resolution it is. So, it's a miss on the benchmark side.