Slow DNS lookup speed means your browser is spending a significant amount of time resolving domain names before a connection attempt even starts. Every time you visit a website, your browser must translate the domain name (like ordoh.com) into an IP address before it can connect. A fast DNS resolver completes this in under 20ms. A slow one can take 200-500ms, adding that delay to every single page you load, multiple times per page for each external resource.
The difference between a fast and slow DNS server is often imperceptible in isolation but becomes noticeable as pages load: images, fonts, scripts, and API calls each require their own DNS lookups if they come from different domains. A page that loads 15 external resources from 10 different domains runs 10 DNS lookups sequentially or in parallel. Shaving 100ms off each lookup adds up to seconds of total page load time improvement.
What Causes Slow DNS Lookup Speed
Your ISP’s DNS server is the most common cause of slow lookups. ISP DNS servers are not optimized for speed. They handle large volumes of queries from all subscribers in a geographic area, are rarely updated to take advantage of DNS performance improvements like anycast routing, and sometimes impose artificial delays for traffic monitoring purposes. Cloudflare’s 1.1.1.1 resolver, by contrast, has an average global response time of under 12ms. Google’s 8.8.8.8 averages around 20ms. Most ISP resolvers average 50-150ms.
A bloated or corrupted local DNS cache adds a different type of slowdown. Windows maintains a DNS cache (managed by the DNS Client service) that stores recently resolved domain names. When this cache grows large or contains corrupted entries, lookups that should be instant (served from cache) take longer as the system searches through stale data. Flushing the cache periodically restores fast cached lookups.
Router DNS relay adds another latency layer. Consumer routers often relay DNS queries from your devices to the upstream DNS server rather than letting devices query the DNS server directly. This adds a hop that contributes 5-30ms per lookup, depending on your router’s hardware. Some routers have buggy DNS relay implementations that add dramatically more latency, especially after extended uptime without a restart.
Switch to a Faster DNS Server
Switching from your ISP’s DNS to a public resolver is the single most impactful change you can make for DNS speed. Cloudflare’s 1.1.1.1 is the fastest globally measured DNS resolver in Cloudflare’s own benchmarks and in independent tests by platforms like DNSPerf.com. Google’s 8.8.8.8 is the most widely used public resolver, with excellent global coverage and consistent low latency.
To change DNS on Windows 11, go to Settings, then Network and Internet, then click your active connection (Wi-Fi or Ethernet). Scroll to DNS server assignment and click Edit. Set to Manual, toggle IPv4 on, enter 1.1.1.1 as the Preferred DNS server and 1.0.0.1 as the Alternate. Click Save. For IPv6, use 2606:4700:4700::1111 and 2606:4700:4700::1001 (Cloudflare’s IPv6 addresses). Run ipconfig /flushdns after changing DNS to clear cached queries to the old resolver.
Changing DNS on Your Router
For a network-wide fix, change the DNS settings on your router instead of individual devices. Log into your router’s admin panel (typically at 192.168.1.1 or 192.168.0.1) and find the DNS settings under WAN or Internet settings. Enter 1.1.1.1 and 1.0.0.1 (or 8.8.8.8 and 8.8.4.4) as the primary and secondary DNS. All devices on your network automatically use the new, faster DNS without any per-device configuration.
Flush the DNS Cache
A bloated DNS cache causes slow cache lookups even when the cached record is valid. Open Command Prompt as administrator and run ipconfig /flushdns. The DNS Resolver Cache is cleared and fresh lookups are made on the next access to each domain. This is a safe operation that does not affect any settings, only clears stored lookup results.
Chrome also maintains its own separate DNS cache. Clear it by visiting chrome://net-internals/#dns and clicking Clear host cache. This is particularly useful if Chrome is slow while other browsers are fast on the same network, as it indicates Chrome’s internal cache has stale entries that its own resolver is struggling with.
Enable DNS over HTTPS in Chrome
DNS over HTTPS (DoH) sends DNS queries encrypted over HTTPS rather than unencrypted UDP. Beyond the privacy benefit, DoH often routes queries through optimized infrastructure that is faster than standard DNS. In Chrome, go to chrome://settings/security, find Use secure DNS, and enable it. Select Cloudflare (1.1.1.1) or Google as your secure DNS provider.
When Chrome uses DoH, it bypasses your system’s DNS configuration entirely and queries the DoH provider directly. This is particularly useful if your ISP is intercepting or manipulating DNS queries, as DoH uses the same HTTPS port (443) that cannot be easily blocked without breaking all HTTPS traffic.
Enable DNS Prefetching in Chrome
Chrome can resolve domain names before you click a link. This DNS prefetching feature runs in the background, resolving all domains linked on the current page so that when you do click a link, the DNS lookup is already complete. Go to chrome://settings/performance and ensure Preload pages for faster browsing and searching is enabled.
DNS prefetching eliminates the perception of slow DNS because by the time you click a link, the IP address is already cached. Pages appear to load instantly. For sites you visit regularly, Chrome also uses predictive prefetching based on your browsing patterns, pre-resolving DNS for likely next-page domains.
Update Your Router Firmware
Router firmware bugs can cause DNS relay delays of 50-200ms per query. Log into your router’s admin panel and check for available firmware updates. Major router brands including ASUS, TP-Link, Netgear, and Linksys release firmware updates that address DNS performance bugs. If a firmware update is not available, restart your router (unplug for 30 seconds) to clear the DNS relay service’s state, which degrades after extended uptime on some models.
If your router supports it, disable the built-in DNS relay entirely and configure devices to query your preferred DNS server (Cloudflare or Google) directly. This removes the router as a latency-adding intermediary in the DNS resolution chain.
Benchmark Your DNS Speed
To measure your actual DNS lookup performance before and after changes, use the free tool namebench (available from Google Code Archive) or DNS Benchmark from Gibson Research Corporation (grc.com). Both tools query dozens of DNS resolvers from your location and rank them by response time. The results tell you exactly which DNS server is fastest for your specific internet connection and geographic location.
namebench typically takes 5-10 minutes and generates a report showing which resolver would give you the best performance. The recommended server varies by region: 1.1.1.1 is fastest in most of North America and Europe, while other providers perform better in Asia or South America depending on your ISP’s network topology.
Frequently Asked Questions
How much does slow DNS affect page load speed?
DNS lookup time adds directly to your time-to-first-byte (TTFB) on every new domain your browser connects to. On a page that loads resources from 10 different domains, a 150ms DNS delay per domain adds 1.5 seconds total. Switching from a 150ms ISP resolver to a 12ms Cloudflare resolver can reduce total DNS time on that same page by over 1.3 seconds, which is measurable in Google PageSpeed Insights and Core Web Vitals.
What is the fastest DNS server in 2025?
According to DNSPerf.com’s global benchmarks, Cloudflare’s 1.1.1.1 consistently ranks as the fastest public DNS resolver globally, with an average response time under 12ms. Google’s 8.8.8.8 averages around 20ms globally and ranks second. NextDNS and Quad9 are alternatives that offer filtering features with slightly higher latency. Your fastest resolver depends on your geographic location and ISP routing.
Does changing DNS servers affect my privacy?
Yes. Your DNS provider can see every domain you visit, even when your actual browsing data is encrypted via HTTPS. Switching from your ISP’s DNS to Cloudflare means Cloudflare sees your queries instead of your ISP. Cloudflare’s 1.1.1.1 service commits to not logging individual IP addresses beyond 25 hours for operational purposes and not selling query data. Google’s 8.8.8.8 uses anonymized query data to improve its services.
Why is DNS lookup slow only in Chrome but not in other browsers?
Chrome maintains its own internal DNS cache separate from the Windows DNS cache. If Chrome’s internal cache is corrupted or contains many entries, cache lookups slow down. Clear Chrome’s DNS cache at chrome://net-internals/#dns by clicking Clear host cache. Also check if a Chrome extension is intercepting DNS queries or blocking pre-resolution. Disabling all extensions and retesting in an incognito window confirms whether Chrome’s extensions are causing the slowdown.
For DNS probe errors that prevent pages from loading entirely, see the article on fixing DNS_PROBE_STARTED. If slow DNS is contributing to full page timeouts, the ERR_TIMED_OUT guide covers the broader timeout troubleshooting process. For connection errors that occur after DNS resolves successfully, the ERR_CONNECTION_REFUSED article explains the next failure stage.
