I understood from Cloudfare's blog post that indeed their recursor service runs in each data center = points of presence. What made you think otherwise?The referenced DCs are presence points aka PoPs. The point of my post was on recursive servers - the servers that are used to build cloudflare's cache for 1.1.1.1/1.0.0.1 services ... These appear to be based in the US which is why content delivered over CDNs is mainly delivered via the US.
So unless cloudflare creates local/regional recursive services in those presence points you referenced, most CDN services will continue to serve you content via the US.
Can you give some examples of URLs where this happens? I'm in Belgium and have not been able to replicate what you describe while using 1.1.1.1. I can understand your theory, but if the Cloudfare PoP is close to your ISP (which it is in my case) and the CDN geolocation knows it is, it should work well even without EDNS Client Subnet?You are totally missing the point. I am getting great query times too but most CDN delivered content is being served from the US versus the nearest CDN PoP.
Please read up on CDN and Anycast DNS with single and multi recursive sources. You'll save me a few grey hairs.
I have tested using the dnsperfbench tool with the -httptest option as mentioned in this blog post:
https://www.sajalkayan.com/post/cloudflare-1dot1dot1dot1.html
The tool can be downloaded here:
https://github.com/turbobytes/dnsperfbench/releases
If I try this, I get a close IP answer from Cloudfare, OpenDNS and Google:
Code:
./dnsperfbench -resolver 195.130.130.1 -httptest https://turbobytes.akamaized.net/static/rum/100kb-image.jpg
+-------------------------------------+--------------------+-------+---------+-------+-------+----------+--------+
| RESOLVER | REMOTE | DNS | CONNECT | TLS | TTFB | TRANSFER | TOTAL |
+-------------------------------------+--------------------+-------+---------+-------+-------+----------+--------+
| 195.130.130.1 (Unknown) | 2.22.55.122:443 | 20ms | 13ms | 41ms | 13ms | 22ms | 108ms |
| 1.1.1.1 (Cloudflare) | 92.122.122.160:443 | 17ms | 15ms | 39ms | 13ms | 25ms | 109ms |
| 208.67.222.222 (OpenDNS) | 2.22.55.120:443 | 26ms | 14ms | 43ms | 13ms | 22ms | 119ms |
| 8.8.8.8 (Google) | 2.22.55.120:443 | 40ms | 15ms | 32ms | 13ms | 21ms | 121ms |
| 185.228.168.168 (Clean Browsing) | 80.239.137.26:443 | 22ms | 21ms | 41ms | 19ms | 22ms | 125ms |
| 9.9.9.9 (Quad9) | 2.16.186.96:443 | 27ms | 22ms | 56ms | 19ms | 28ms | 152ms |
| 8.26.56.26 (Comodo) | 104.86.110.185:443 | 32ms | 22ms | 50ms | 20ms | 29ms | 153ms |
| 199.85.126.20 (Norton) | 72.247.178.27:443 | 27ms | 28ms | 54ms | 23ms | 30ms | 162ms |
| 114.114.114.114 (114dns) | 23.215.104.203:443 | 133ms | 117ms | 239ms | 120ms | 162ms | 772ms |
| 119.29.29.29 (DNSPod) | 223.119.50.201:443 | 125ms | 220ms | 473ms | 219ms | 309ms | 1.346s |
| 180.76.76.76 (Baidu) | 23.2.16.27:443 | 294ms | 229ms | 471ms | 231ms | 324ms | 1.549s |
| [2001:4860:4860::8888] (Google) | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL |
| [2606:4700:4700::1111] (Cloudflare) | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL |
| [2a0d:2a00:1::] (Clean Browsing) | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL |
| [2620:fe::fe] (Quad9) | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL |
| [2620:0:ccc::2] (OpenDNS) | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL | FAIL |
+-------------------------------------+--------------------+-------+---------+-------+-------+----------+--------+
The average ping to the answer above from my local ISP as well as to those from Cloudflare, OpenDNS and Google was 12 ms. The average ping to the answer from Quad9 was 19 ms in this case.
Maybe others can give it a try from their connection to compare? Or could you try it with a URL of something that you got served from the US instead of your nearest CDN PoP? Note that the Windows version that can be downloaded does not seem to give reliable results with the -httptest option. I tested with the Linux binary.
Last edited: