DNS Speed Test
Benchmark resolver latency across Cloudflare, Google, Quad9, OpenDNS & more
Advertisement · Anuncio
Every web page load begins with one or more DNS lookups. Before your browser can connect to a website, it must resolve the domain name to an IP address. This lookup happens sequentially — the browser cannot begin downloading any resource until DNS resolves. On a page that loads assets from five different domains, DNS latency compounds across all five lookups. Research by Akamai found that a 100ms increase in page load time correlates with a 7% reduction in conversion rates.
Major providers like Cloudflare and Google deploy anycast routing — the same IP (e.g., 1.1.1.1) is simultaneously announced from hundreds of data centers. BGP automatically routes your queries to the nearest node. However, BGP routing isn't perfectly optimal — peering agreements and congestion can cause suboptimal paths. Empirical testing from your actual network is the only reliable method to identify your fastest resolver.
DNS records include a Time-To-Live (TTL) — the number of seconds a resolver caches the record. Common TTL values range from 300 seconds to 86,400 seconds. While cached, DNS lookups return instantly with zero network latency. Your OS, browser, and the resolver itself all maintain caches. This means frequently visited domains rarely incur full lookup latency on repeat visits.
The servers tested here are recursive resolvers — they accept queries from end users and perform the complete resolution process, querying root servers, TLD servers, and authoritative servers as needed. Authoritative nameservers hold the actual DNS records for specific domains. The latency measured is the recursive resolver's total response time, including cache hits and misses.
Anycast assigns a single IP address to multiple servers in different locations. When you send a packet to an anycast address, routers automatically forward it to the "nearest" server based on BGP. Cloudflare operates over 300 anycast nodes; Google over 200. This architecture provides excellent geographic distribution and resilience — if one data center goes down, traffic reroutes automatically.
Why do results vary between runs?
DNS response times fluctuate due to resolver cache state (a cached record returns instantly), network congestion, BGP route changes, and server load. Run multiple tests at different times and average the results for reliable benchmarking.
Does faster DNS improve gaming?
DNS speed affects game connection startup — when you first connect to a game server, DNS resolves the hostname. A 100ms faster DNS lookup means 100ms faster loading. However, once connected, DNS has no effect on ping — that depends on the network path to the game server.
What does "Timeout" mean?
The DNS server did not respond within the timeout window. This can occur because the server is temporarily unreachable, filtering queries from the test server, or network conditions caused packet loss. A single timeout does not mean the server is unreliable — retry if you see unexpected timeouts.
Should I use IPv4 or IPv6 DNS addresses?
There is no performance difference — DNS protocol performance is identical regardless of transport address. The choice matters for consistency: if your device prefers IPv6 connections, using IPv6 DNS avoids a protocol mismatch.
How do I permanently change my DNS?
For broadest impact, change DNS on your router — this applies to every device on your network. On Windows: Network Settings → IPv4 Properties → DNS. On macOS: System Preferences → Network → Advanced → DNS. On Android 9+: Settings → Network → Private DNS.