{"id":4529,"date":"2026-06-06T14:10:10","date_gmt":"2026-06-06T14:10:10","guid":{"rendered":"https:\/\/www.copahost.com\/blog\/?p=4529"},"modified":"2026-06-06T20:09:58","modified_gmt":"2026-06-06T20:09:58","slug":"how-to-fix-slow-dns-lookup","status":"publish","type":"post","link":"https:\/\/www.copahost.com\/blog\/how-to-fix-slow-dns-lookup\/","title":{"rendered":"How to Fix Slow DNS Lookup: A Complete Speed Guide"},"content":{"rendered":"\n

Before a single image, line of text, or button appears on a web page, your device has to do something invisible: translate the domain name into an IP address. That step is the DNS lookup \u2014 and when it’s slow, everything<\/em> waits. No server response, no rendering, no interaction until the name is resolved.<\/p>\n\n\n\n

A sluggish DNS<\/a> lookup can quietly add a noticeable delay to every page load, hurting user experience and even search rankings. The good news: most causes are easy to diagnose and fix, often in minutes and at no cost. This guide walks through why DNS lookups slow down, how to measure yours, and exactly how to fix it \u2014 whether you’re a regular user or a site owner.<\/p>\n\n\n\n

What is a DNS lookup (and why speed matters)<\/h2>\n\n\n\n

The Domain Name System (DNS) is the phone book of the internet: it converts a human-friendly name like copahost.com<\/code> into the numeric IP address that computers use to connect. Every time you open a site your device hasn’t visited recently, it sends a query to a DNS server and waits for the answer before it can load anything.<\/p>\n\n\n\n

That wait is small, but it’s on the critical path. Industry performance research indicates DNS resolution can account for a meaningful share of total page load time on a first visit \u2014 and on a slow resolver, the difference between a fast lookup and a slow one is dramatic.<\/p>\n\n\n\n

\n

Typical DNS response time by resolver<\/h3>\n

Lower is better. Approximate ranges for an uncached query.<\/p>\n\n

\n
\n Typical ISP DNS<\/strong><\/span>~80\u2013200 ms<\/span>\n <\/div>\n
\n
<\/div>\n <\/div>\n <\/div>\n\n
\n
\n Public DNS (Cloudflare \/ Google)<\/strong><\/span>~8\u201320 ms<\/span>\n <\/div>\n
\n
<\/div>\n <\/div>\n <\/div>\n\n
\n
\n Cached locally<\/strong><\/span>< 1 ms<\/span>\n <\/div>\n
\n
<\/div>\n <\/div>\n <\/div>\n\n

Values are typical industry ranges and vary by location and network. The takeaway is the order of magnitude: a public resolver can be many times faster than a default ISP server, and a cached result is effectively instant.<\/p>\n<\/div>\n\n\n\n

\n
⏱️<\/div>\n
\n Rule of thumb<\/strong>\n

A DNS lookup under 50 ms<\/strong> is usually imperceptible. Around 100 ms<\/strong> it becomes noticeable. Consistently over 150 ms<\/strong> starts to hurt perceived performance \u2014 and is your signal to apply the fixes below.<\/p>\n <\/div>\n<\/div>\n\n\n\n

What causes a slow DNS lookup?<\/h2>\n\n\n\n

Slow resolution usually traces back to one of a handful of causes. As with most network issues, they split between problems on your side<\/strong> (the resolver and device you use) and problems on the website’s side<\/strong> (how the domain’s DNS is configured).<\/p>\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n
Cause<\/th>\n What happens<\/th>\n Side<\/th>\n <\/tr>\n <\/thead>\n
Slow ISP resolver<\/strong><\/td>\n Default ISP DNS servers are often slower and less optimized than public ones.<\/td>\n Your side<\/td>\n <\/tr>\n
Geographic distance<\/strong><\/td>\n The farther the DNS server, the longer each query takes to travel.<\/td>\n Your side<\/td>\n <\/tr>\n
Outdated \/ bloated DNS cache<\/strong><\/td>\n Stale or corrupted local cache entries cause delays and re-lookups.<\/td>\n Your side<\/td>\n <\/tr>\n
Too many external domains<\/strong><\/td>\n Each third-party script, font, or tracker triggers its own lookup.<\/td>\n Website side<\/td>\n <\/tr>\n
Excessive CNAME chaining<\/strong><\/td>\n Multiple redirects between records add hops to every resolution.<\/td>\n Website side<\/td>\n <\/tr>\n
Overloaded nameservers<\/strong><\/td>\n Slow or low-tier nameservers at the host delay responses for all visitors.<\/td>\n Website side<\/td>\n <\/tr>\n
TTL set too low<\/strong><\/td>\n Very short TTLs force resolvers to re-query constantly instead of caching.<\/td>\n Website side<\/td>\n <\/tr>\n
DNSSEC \/ TCP overhead<\/strong><\/td>\n Validation and TCP fallback can add latency if misconfigured.<\/td>\n Website side<\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n\n\n\n

How to measure your DNS lookup time first<\/h2>\n\n\n\n

Don’t guess \u2014 measure. Knowing your current lookup time tells you whether you have a problem and lets you confirm the fix actually worked.<\/p>\n\n\n\n\n \n \n \n \n \n \n \n
Method<\/th>\n How to use it<\/th>\n <\/tr>\n <\/thead>\n
Browser DevTools<\/td>\n Press F12<\/code> \u2192 Network<\/strong> tab \u2192 click any request \u2192 Timing<\/strong> section \u2192 read the DNS Lookup<\/em> row.<\/td>\n <\/tr>\n
dig (Linux \/ macOS)<\/span><\/td>\n Run dig copahost.com<\/code> and read the Query time<\/em> value at the bottom.<\/td>\n <\/tr>\n
nslookup (Windows)<\/span><\/td>\n Run nslookup copahost.com<\/code> to confirm which server answered and how.<\/td>\n <\/tr>\n
Online tools<\/td>\n Use a DNS benchmark or checker to compare resolvers and propagation<\/a> across regions.<\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n\n\n\n

If your lookups are consistently above 100 ms, your resolver is the likely bottleneck \u2014 start with the very first fix below.<\/p>\n\n\n\n

How to fix slow DNS lookup (your side)<\/h2>\n\n\n\n

1. Switch to a faster public DNS server<\/h3>\n\n\n\n

This is the single most impactful fix for most people. ISP resolvers commonly respond in 80\u2013200 ms; major public resolvers often respond in 8\u201320 ms \u2014 roughly a tenfold improvement on every query. Pick one and set it on your device or, better, your router.<\/p>\n\n\n\n\n \n \n \n \n \n \n
Provider<\/th>\n Preferred<\/th>\n Alternate<\/th>\n Note<\/th>\n <\/tr>\n <\/thead>\n
Cloudflare<\/td>\n 1.1.1.1<\/code><\/td>\n 1.0.0.1<\/code><\/td>\n Privacy-focused, very fast<\/td>\n <\/tr>\n
Google Public DNS<\/td>\n 8.8.8.8<\/code><\/td>\n 8.8.4.4<\/code><\/td>\n Reliable, globally distributed<\/td>\n <\/tr>\n
Quad9<\/td>\n 9.9.9.9<\/code><\/td>\n 149.112.112.112<\/code><\/td>\n Adds security filtering<\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n\n\n\n
\n
💡<\/div>\n
\n Tip \u2014 fix it once, at the router<\/strong>\n

Changing DNS in your router’s admin panel (usually 192.168.1.1<\/code>) applies the faster resolver to every device on the network \u2014 phones, smart TVs, consoles \u2014 without configuring each one manually.<\/p>\n <\/div>\n<\/div>\n\n\n\n

2. Flush your DNS cache<\/h3>\n\n\n\n

A stale or corrupted local cache can serve slow or wrong records. Clearing it forces fresh, accurate resolution.<\/p>\n\n\n\n\n \n \n \n \n \n \n
System<\/th>\n Command<\/th>\n <\/tr>\n <\/thead>\n
Windows<\/td>\n ipconfig \/flushdns<\/code><\/td>\n <\/tr>\n
macOS<\/td>\n sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/code><\/td>\n <\/tr>\n
Chrome (own cache)<\/span><\/td>\n Open chrome:\/\/net-internals\/#dns<\/code> \u2192 Clear host cache<\/strong><\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n\n\n\n

3. Use a local caching resolver (advanced)<\/h3>\n\n\n\n

Power users on Linux can run a local caching resolver such as Unbound or systemd-resolved, which keeps recent answers close and dramatically cuts repeat lookup times. Tools like Pi-hole also cache DNS network-wide while filtering ads.<\/p>\n\n\n\n

4. Clean up your network path<\/h3>\n\n\n\n

Disable unused or unknown network adapters so traffic takes the correct, fast route. On laptops that travel between networks, configuring DNS per-device (rather than only on one router) keeps speed consistent wherever you connect.<\/p>\n\n\n\n

How to fix slow DNS lookup (website owner side)<\/h2>\n\n\n\n

If visitors experience slow loads everywhere, the bottleneck is in your domain’s DNS setup. These fixes benefit every visitor on every page load.<\/p>\n\n\n\n

5. Move to a premium \/ global DNS network<\/h3>\n\n\n\n

Free DNS bundled with low-tier shared hosting is often not optimized for speed. Premium or globally distributed DNS (such as Cloudflare’s network) serves answers from the location closest to each visitor, cutting latency worldwide. For most small-to-medium sites, this is the most effective single improvement available.<\/p>\n\n\n\n

6. Tune your TTL values<\/h3>\n\n\n\n

TTL (Time To Live) controls how long resolvers cache your records. Too low and visitors re-query constantly; too high and updates take too long to apply. Balance the two.<\/p>\n\n\n\n\n \n \n \n \n \n \n
TTL value<\/th>\n Effect<\/th>\n Best for<\/th>\n <\/tr>\n <\/thead>\n
300s<\/code> (5 min)<\/span><\/td>\n Frequent re-lookups; fast to update<\/td>\n Records you’re about to change<\/td>\n <\/tr>\n
3600s<\/code> (1 hour)<\/span><\/td>\n Balanced caching and flexibility<\/td>\n Most general-purpose records<\/td>\n <\/tr>\n
86400s<\/code> (24 hours)<\/span><\/td>\n Heavy caching; slow to update<\/td>\n Stable records that rarely change<\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n\n\n\n

7. Reduce external domains and CNAME chains<\/h3>\n\n\n\n

Every third-party script, font, analytics tag, or tracker on your page triggers its own DNS lookup. Auditing and removing unnecessary external domains<\/a> lowers total resolution time. Likewise, flattening long chains of CNAME redirects removes extra hops from each query.<\/p>\n\n\n\n

8. Add dns-prefetch and preconnect hints<\/h3>\n\n\n\n

For the external domains you do keep, tell the browser to resolve them early. Adding resource hints<\/a> in your page’s <head><\/code> lets DNS resolution start before the asset is actually needed, shaving time off the critical path.<\/p>\n\n\n\n

Example:<\/p>\n\n\n

<link<\/span> rel<\/span>=\"dns-prefetch\"<\/span> href<\/span>=\"https:\/\/fonts.example.com\"<\/span>><\/span>\n<link<\/span> rel<\/span>=\"preconnect\"<\/span> href<\/span>=\"https:\/\/fonts.example.com\"<\/span> crossorigin<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Where DNS sits in a page load<\/h2>\n\n\n\n
Understanding the order helps explain why DNS is so impactful: it’s one of the very first steps, and nothing else can start until it finishes.<\/p>\n\n\n\n
\n  
\n    
1<\/div>\n    
DNS lookup<\/strong> \u2014 translate the domain into an IP address \u2190 the focus of this guide<\/span><\/div>\n  <\/div>\n  
\u2193<\/div>\n\n  
\n    
2<\/div>\n    
TCP connection<\/strong> \u2014 open a connection to that IP address<\/div>\n  <\/div>\n  
\u2193<\/div>\n\n  
\n    
3<\/div>\n    
TLS handshake<\/strong> \u2014 establish the secure (HTTPS) connection<\/div>\n  <\/div>\n  
\u2193<\/div>\n\n  
\n    
4<\/div>\n    
Content download<\/strong> \u2014 server sends the page, and it renders<\/div>\n  <\/div>\n\n  
Because DNS is step 1, a slow lookup delays steps 2, 3, and 4. This is why a site with powerful hosting and optimized code can still feel slow when DNS resolution lags.<\/p>\n<\/div>\n\n\n\n
Does slow DNS affect SEO?<\/h2>\n\n\n\n
Indirectly, yes. Google uses Core Web Vitals as a ranking signal, and Time to First Byte (TTFB) is influenced by DNS lookup speed. Faster DNS lowers TTFB, which can improve Largest Contentful Paint (LCP) \u2014 one of the metrics Google measures. Adding preconnect hints also reduces perceived load time for above-the-fold content. In short: faster DNS is good for users and<\/em> for rankings.<\/p>\n\n\n\n
\n  
💡<\/div>\n  
\n    Tip<\/strong>\n    
Much of DNS performance is decided by your host. A provider with fast, well-configured, globally reachable nameservers removes this bottleneck before it ever reaches your visitors. Copahost<\/a> sets up your domain’s DNS for speed and reliability from day one.<\/p>\n  <\/div>\n<\/div>\n\n\n\n
\n  
⚡<\/div>\n  
Fast DNS starts with the right host<\/p>\n  
\n    Copahost web hosting comes with fast, well-configured, globally reachable nameservers \u2014 so DNS never becomes the bottleneck that slows down your visitors. Reliable speed, set up correctly from day one.\n  <\/p>\n  \n    Explore Copahost web hosting \u2192\n  <\/a>\n<\/div>\n\n\n\n
Frequently asked questions about slow DNS lookups<\/h2>\n\n\n\n
\n\n\n  
\n    What causes a slow DNS lookup?<\/summary>\n    
The most common cause is a slow default DNS server assigned by your ISP. Other causes include geographic distance to the DNS server, an outdated local DNS cache, too many external domains on a page, excessive CNAME chaining, overloaded nameservers at the host, and TTL values set too low. Causes split between your side (resolver and device) and the website side (DNS configuration).<\/p>\n  <\/details>\n\n  
\n    What is a good DNS lookup time?<\/summary>\n    
A cached lookup should be under 1 ms, and a fresh lookup from a fast public resolver typically lands around 8\u201320 ms. As a rule of thumb, anything under 50 ms is imperceptible, around 100 ms becomes noticeable, and consistently over 150 ms starts to hurt performance and is worth fixing.<\/p>\n  <\/details>\n\n  
\n    How do I check my DNS lookup speed?<\/summary>\n    
In any browser, press F12 to open DevTools, go to the Network tab, click a request, and read the DNS Lookup row in the Timing section. On Linux or macOS you can run “dig” and read the Query time value; on Windows use “nslookup”. Online DNS benchmark tools also let you compare resolvers.<\/p>\n  <\/details>\n\n  
\n    What’s the single best fix for slow DNS?<\/summary>\n    
For most users, switching from your ISP’s default DNS to a fast public resolver such as Cloudflare (1.1.1.1) or Google (8.8.8.8) is the most impactful change, often improving response time roughly tenfold. For website owners, moving the domain’s nameservers to a fast, globally distributed DNS network is usually the most effective improvement.<\/p>\n  <\/details>\n\n  
\n    Should I change DNS on my router or each device?<\/summary>\n    
Changing it on the router is the most efficient option because it automatically applies the faster DNS to every device on your network. Configuring individual devices is better for laptops that frequently move between different networks, so they keep fast DNS wherever they connect.<\/p>\n  <\/details>\n\n  
\n    Does flushing the DNS cache speed things up?<\/summary>\n    
It can, when the slowdown is caused by stale or corrupted cache entries. Flushing forces fresh resolution and accurate testing. It won’t make a fundamentally slow resolver fast, but it’s a quick, safe first step and is useful before measuring your lookup time.<\/p>\n  <\/details>\n\n  
\n    Does slow DNS affect SEO?<\/summary>\n    
Indirectly, yes. DNS lookup speed affects Time to First Byte, which influences Largest Contentful Paint \u2014 one of Google’s Core Web Vitals ranking signals. Faster DNS, combined with preconnect and dns-prefetch hints, reduces load time and can have a positive effect on rankings.<\/p>\n  <\/details>\n\n  
\n    How can a website owner reduce DNS lookups?<\/summary>\n    
Reduce the number of external domains (third-party scripts, fonts, trackers), since each one triggers its own lookup. Flatten long CNAME chains, use a premium globally distributed DNS network, set balanced TTL values, and add dns-prefetch and preconnect hints for the external domains you keep.<\/p>\n  <\/details>\n\n<\/section>\n\n\n\n\n