![]() The stated reason for Cloudflare to not support ECS is a privacy concern, but since Cloudflare is also a CDN provider pushing the use of anycast where one IP is applicable for multiple regions worldwide, you can see they have a business angle too. ![]() The downside is, it's possible that the returned IP is less optimized than ISP's default DNS or with ECS, where theoretically the returned IP can be tailored to ISP's local CDN. Without ECS, any user of a particular node should get the same answer regardless of their origin IP, this means Cloudflare's cache is applicable for the entire node. So, Cached indicates the latency between your computer and the nearest node of the DNS server plus their DB lookup speed (which is probably less than 1 ms), this is the fastest possible resolving speed you can get without having a local instance of pi-hole, AdGuard Home, unbound etc.Ĭloudflare has an advantage in Cached because they don't support ECS. The speed for querying these nameservers for popular sites is what Uncached means. The TLD nameserver gives the nameserver of the second-level domain (in our example, the example.test), where the resolver then queries for the next level of the domain (in our example, the full ). This is what DotCom means in the benchmark. com, so all it takes is how long it takes for them to query the. com TLD, it's unlikely they need to do that for. test, which doesn't exist IRL), assuming they don't have a current cache for that TLD nameserver IP. If they don't have the record for the domain you asked for, they'll then need to query the root nameserver to ask for the TLD (top-level domain) nameserver (in this case, the. This is what Cached means in the GRC DNS benchmark. This is where using a popular DNS server is advantageous compared to a rarely used DNS server, most of the time, the domain you look up to has been requested by another user and you only wait for the DNS server to immediately return the answer from their cache. When you ask for, they will check if they already have a current (because every answer has a predefined TTL (time to live) before it expires and must be requested again) record for it in their cache. To grok what they mean, first, you need to understand that both Google and Cloudflare are recursive resolvers. The benchmark result for the GRC tool is explained here. How does this affect speed? I think I read that streaming sites are the ones that benefit the most from this. I can definitely confirm that Google DNS has this feature while Cloudflare does not which is what both exactly say in their respective documentation. Anybody here that can explain what these 3 values mean and what I should really be looking at?Īs for ECS, I tested it using nslookup -type=TXT following the instruction from Amazon AWS. For Uncached and DotCom, Google is 1.5 to 2 times faster than Cloudflare. I was not able to notice any difference when it comes to regular browsing but there are huge differences when it comes to DNS benchmark.įor Cached, Cloudflare is definitely faster, almost as fast as my ISP DNS Google is around 20ms slower. Now, I've been reading about Cloudflare's DNS and how better it is both in speed and privacy especially with how aggressive Google is against your privacy and I decided to give it a try. I'm no expert on networks and nothing more than a regular user so please bear with me. It's more reliable than my ISP DNS here which I was able to test from time to time when I reset my router and forgot to configure DNS settings. ![]() I have always used Google DNS with no issues for the past 10+ years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |