How to Fix Slow DNS Lookup: Causes, Tests & Solutions

Last Updated: May 2026

A slow DNS lookup can make your internet feel slow even when your actual connection speed is fine. You may open a website and see the browser stuck on messages such as “resolving host,” “looking up,” or “waiting for DNS.” This delay often happens before the page starts loading because your device is taking too long to find the correct IP address for the domain name. Learning How to Fix Slow DNS Lookup is important for everyday users, website owners, bloggers, developers, SEO teams, and businesses.

DNS performance can affect browsing speed, page experience, website loading time, and user trust. Google Public DNS explains that DNS latency can be affected by client-to-resolver latency, resolver-to-name-server latency, cache misses, and resolver capacity.

DNS stands for Domain Name System. It works like the internet’s address book. When you type a website name into your browser, DNS translates that domain into an IP address so your device can connect to the correct server. If this lookup process is slow, the website may feel slow before images, text, scripts, or videos even begin loading.

This complete guide explains the causes, tests, and solutions for slow DNS lookup. It also covers DNS cache layers, DNS propagation, secure DNS, best DNS servers, Core Web Vitals, resource hints, WordPress fixes, and practical troubleshooting steps.

Quick Answer: How to Fix Slow DNS Lookup

The fastest way to fix slow DNS lookup is to identify whether the delay is coming from your browser, device, router, ISP DNS resolver, VPN, or the website’s DNS configuration. Start by restarting your browser and router, flushing DNS cache, testing another DNS resolver, disabling VPN temporarily, and checking DNS timing with tools like Chrome DevTools, nslookup, or dig.

What Is DNS Lookup?

DNS lookup is the process of finding the IP address connected to a domain name. People remember domain names like example.com, but computers connect through IP addresses. When you open a website, your browser needs DNS to find where that website is hosted.

A basic DNS lookup works like this:

1. You type a website address into your browser.
2. The browser checks whether it already has a cached DNS answer.
3. The operating system checks its local DNS cache.
4. The router or DNS resolver may check its cache.
5. If no cached result exists, the resolver contacts other DNS servers.
6. The correct IP address is returned.
7. The browser starts connecting to the website server.

If the answer is already cached, DNS lookup is usually fast. If the resolver must contact other name servers, the lookup can take longer. Google Public DNS explains that cache misses can increase DNS latency because the resolver may need to ask other servers before returning an answer.

DNS Lookup vs TTFB vs Full Page Load Time

Before learning How to Fix Slow DNS Lookup, it is important to understand what DNS lookup is not. DNS lookup is only one part of the page loading process. A website can be slow because of DNS, hosting, redirects, server response, JavaScript, images, ads, fonts, or third-party scripts.

A slow DNS lookup delays the beginning of the connection. A slow TTFB means the server is slow to respond after connection. A slow full page load means the website has heavy resources, render-blocking files, large images, or too many scripts.

This distinction helps users avoid blaming DNS for every slow website problem.

DNS Cache Layers Explained

DNS cache is useful because it saves previous lookup results and avoids repeating the full DNS process every time a website is opened. However, old or broken cache entries can also cause delays or incorrect results.

Possible DNS cache problems include outdated records, router forwarding bugs, ISP resolver delay, resolver cache misses, or slow authoritative DNS response. Google Public DNS notes that caching strategy matters because cache misses can add considerable latency when a resolver must recursively query other name servers.

Common Signs of Slow DNS Lookup

Slow DNS lookup often feels like a general internet problem. These signs can help you identify it:

Main Causes of Slow DNS Lookup

1. Slow ISP DNS Resolver

Most users automatically use DNS servers provided by their internet service provider. Sometimes these resolvers work well. Other times they may be slow, overloaded, filtered, or poorly routed.

DNS speed depends on several factors, including distance from the resolver, resolver load, network congestion, cache hit rate, and how quickly the resolver can contact authoritative name servers. Google Public DNS lists cache misses and resolver underprovisioning as common reasons DNS responses can become slow.

2. Old or Corrupted DNS Cache

Your browser, operating system, router, and resolver may store DNS records. This usually improves speed, but old DNS cache can cause issues after a website changes hosting, moves to a CDN, updates nameservers, or changes IP addresses.

If only one device is affected, flushing DNS cache is a good first step. Microsoft describes ipconfig as a command that displays TCP/IP configuration values and refreshes DHCP and DNS settings.

3. Router DNS Problems

Your router may forward DNS requests from all connected devices. If all devices on your Wi-Fi have slow DNS lookup, the router or ISP DNS settings may be the cause.

Common router DNS problems include:

• Old firmware
• Weak router hardware
• Overheating
• DNS forwarding bugs
• Incorrect IPv6 DNS settings
• Too many connected devices
• ISP DNS outages
• Changed router DNS settings

Restarting the router can help, but if the problem returns, update the router firmware and check DNS settings.

4. VPN or Proxy Delay

VPNs and proxies often route DNS requests through their own servers. This can improve privacy, but it can also slow DNS if the VPN server is far away, overloaded, or using a weak resolver.

Test the same website with VPN on and off. If DNS lookup becomes faster without VPN, try a closer VPN server or check DNS leak protection settings.

5. Too Many Third-Party Domains

Modern websites often load resources from many domains, including analytics tools, ads, fonts, video players, chat widgets, CDNs, payment tools, and social embeds. Each new domain may require a DNS lookup.

Website owners should reduce unnecessary external domains because complex pages can create extra DNS work before the page fully loads. Resource hints such as preconnect and dns-prefetch can also help browsers prepare important connections earlier when used correctly.

6. Slow Authoritative DNS Provider

If you own a website, your authoritative DNS provider matters. A resolver eventually depends on the authoritative DNS provider when the answer is not already cached.

Choose a DNS provider with:

• Global anycast DNS
• Strong uptime
• Fast response times
• DNSSEC support
• Easy record management
• Monitoring options
• Reliable support

A slow authoritative DNS provider can affect first-time visitors when records are not already cached.

7. Long CNAME Chains

A CNAME record points one domain to another. CNAME records are common for CDNs, SaaS tools, landing page builders, hosted apps, and tracking platforms.

A long CNAME chain can create extra DNS work.

Example:

www.example.com
→ example.hostedplatform.com
→ platform.edge.cdn.net
→ region.provider.net
→ final IP address

A cleaner setup keeps the DNS path shorter whenever possible.

8. Poor TTL Settings

TTL means Time To Live. It controls how long DNS records stay cached by DNS resolvers before they should be refreshed.

Cloudflare explains that proxied DNS records use an Auto TTL of 300 seconds, while DNS-only records can usually be customized. This matters because TTL controls how long recursive resolvers cache DNS answers before checking for updates.

Very low TTL values can reduce caching benefits because resolvers must refresh records more often. Very high TTL values can make DNS changes slower to appear after migrations.

9. DNS Propagation After Migration

DNS propagation and slow DNS lookup are related, but they are not the same.

Slow DNS lookup means the browser or resolver is taking too long to find the IP address.

DNS propagation means DNS changes have not reached all users or resolvers yet after a record update.

For example, if you recently changed hosting, moved to a CDN, changed nameservers, or updated an A record, some users may still receive old DNS records until cached records expire. TTL plays an important role in this process because it controls how long DNS records can remain cached.

10. IPv6 Misconfiguration

Some networks use both IPv4 and IPv6. If IPv6 DNS or routing is misconfigured, a browser may try IPv6 first, wait, and then fall back to IPv4. This can look like slow DNS or slow connection startup.

Possible signs include:

• Slow loading only on one Wi-Fi network
• Mobile data works better than home Wi-Fi
• Some websites are slow while others are fine
• VPN changes the result
• AAAA records behave differently from A records

11. Malware or DNS Hijacking

Malware, adware, or suspicious browser extensions can change DNS settings. Attackers may also modify router DNS settings to redirect users to fake pages.

Warning signs include:

• Unknown DNS servers in settings
• Search redirects
• Random pop-ups
• Browser homepage changes
• DNS settings changing automatically
• Different DNS results on one device compared with others

If DNS settings keep changing without your permission, scan your device, remove suspicious extensions, reset your browser, and check router DNS settings.

How to Measure DNS Lookup Time Correctly

To properly understand How to Fix Slow DNS Lookup, measure DNS time before changing settings.

In browser performance data, DNS lookup timing can be checked using domainLookupStart and domainLookupEnd. MDN explains that domainLookupStart returns the timestamp immediately before the browser starts DNS lookup, while domainLookupEnd returns the timestamp immediately after the browser finishes the domain lookup.

Use this formula:

DNS Lookup Time = domainLookupEnd - domainLookupStart

If the value is high, DNS may be slowing the page. If the value is zero, MDN notes that the resource may have been retrieved from cache or may be a cross-origin request without the required timing permission header.

How to Test Slow DNS Lookup

Test 1: Use Chrome DevTools Network Timing

Chrome DevTools can help you inspect how a page loads. Google’s Chrome DevTools documentation says the Network panel includes a Timing tab that shows a breakdown of network activity for a selected resource.

Steps:

1. Open Chrome.
2. Visit the slow website.
3. Right-click and choose Inspect.
4. Open the Network tab.
5. Reload the page.
6. Click the main document request.
7. Open the Timing section.
8. Check DNS lookup timing.

If DNS time is high, DNS may be part of the problem. If DNS time is low but waiting time is high, the problem may be hosting, backend performance, database delay, CDN setup, or server response.

Test 2: Use nslookup

nslookup helps diagnose DNS infrastructure. Microsoft describes nslookup as a command-line tool that displays information useful for diagnosing DNS infrastructure.

Use this command:

nslookup example.com

Test specific DNS resolvers:

nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1
nslookup example.com 9.9.9.9

Compare the results. If one resolver is much slower or fails, the resolver may be the problem.

Test 3: Use dig

On macOS and Linux, dig is commonly used for DNS testing.

dig example.com

Test with specific resolvers:

dig example.com @8.8.8.8
dig example.com @1.1.1.1
dig example.com @9.9.9.9

Look for query time. Run the test more than once. The first lookup may be slower because the answer is not cached. Later lookups may be faster because the resolver cached the answer.

Test 4: Compare Wi-Fi and Mobile Data

If a website loads slowly on Wi-Fi but quickly on mobile data, your router, ISP DNS, or Wi-Fi network may be the issue.

Steps:

1. Open the same website on Wi-Fi.
2. Turn off Wi-Fi.
3. Load the website using mobile data.
4. Compare speed.
5. Restart the router if Wi-Fi is slower.
6. Test another DNS resolver.

Test 5: Try Another Browser

If the issue happens only in one browser, the problem may be browser cache, extensions, secure DNS settings, or a damaged browser profile.

Test with:

• Chrome
• Edge
• Firefox
• Safari
• Incognito or private mode

If private mode is faster, disable extensions and clear browser data.

How to Fix Slow DNS Lookup Step by Step

Step 1: Restart the Browser

Close the browser completely and reopen it. This can clear temporary browser-level DNS and connection issues. It is a simple first step before changing system settings.

Step 2: Restart the Router

If multiple devices are slow, restart the router.

1. Turn off the router.
2. Wait 30 seconds.
3. Turn it back on.
4. Wait for the connection to stabilize.
5. Test the website again.

Restarting the router can clear temporary DNS forwarding problems and refresh the network connection.

Step 3: Flush DNS Cache on Windows

Open Command Prompt as administrator and run:

ipconfig /flushdns

Then restart the browser and test again. Microsoft’s ipconfig documentation confirms that the command refreshes DNS settings.

Step 4: Flush DNS Cache on macOS

Open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your password if asked. Then restart the browser and test the website again.

Step 5: Flush DNS Cache on Linux

For many Linux systems using systemd-resolved, try:

sudo resolvectl flush-caches

Ubuntu’s systemd-resolved manpage says resolvectl flush-caches is the recommended synchronous way to flush caches maintained by systemd-resolved.

Step 6: Disable VPN Temporarily

Turn off your VPN and reload the website. If DNS lookup becomes faster, the VPN DNS route may be slow.

Possible fixes:

• Choose a closer VPN server
• Update the VPN app
• Check split tunneling
• Disable unnecessary filtering
• Contact VPN support

Step 7: Check Proxy Settings

Incorrect proxy settings can delay browsing.

On Windows:

1. Open Settings.
2. Go to Network & Internet.
3. Open Proxy.
4. Disable unknown manual proxy settings.

On macOS:

1. Open System Settings.
2. Go to Network.
3. Select your connection.
4. Check proxy settings.
5. Remove unknown proxy entries.

Step 8: Scan for Malware

If DNS settings keep changing or websites redirect strangely, run a trusted security scan and check router DNS settings.

Also check:

• Browser extensions
• Recently installed software
• Router admin password
• DNS server values in router settings
• Unknown startup programs
• Unwanted browser profiles

Change DNS Resolver

If your ISP DNS resolver is slow, test a trusted public DNS resolver. Google explains that users must explicitly change DNS settings to use Google Public DNS instead of the DNS servers assigned automatically by their ISP.

Before changing DNS, write down your current DNS settings so you can restore them later if needed.

Best DNS Servers Comparison

Google lists 8.8.8.8 and 8.8.4.4 as Google Public DNS addresses. Cloudflare lists 1.1.1.1 and 1.0.0.1 as its standard resolver addresses and describes the standard resolver as fast, private DNS with no content filtering. Quad9 describes itself as a free recursive DNS service that can block malicious hostnames.

Changing DNS does not increase your raw download speed, but it can reduce lookup delay if your current resolver is slow, overloaded, or poorly routed.

Secure DNS, DoH and DoT: Should You Use Them?

Secure DNS can improve privacy and security, but it does not always guarantee faster lookup speed.

DNS-over-HTTPS, also called DoH, sends DNS queries through HTTPS. DNS-over-TLS, also called DoT, encrypts DNS queries using TLS. Google Public DNS states that it supports DNS over TLS and DNS over HTTPS for greater security and privacy.

Use Secure DNS when:

• You want better privacy on public Wi-Fi
• Your ISP DNS is unreliable
• You want encrypted DNS queries
• You trust the DNS provider you are using

Be careful when:

• You are on a school, office, or managed network
• Parental controls depend on DNS filtering
• VPN or security software already manages DNS
• Secure DNS makes internal websites stop working
• Your network blocks DoH or DoT traffic

Secure DNS is useful, but it should be tested on your network. If it slows browsing or breaks internal resources, switch back to your previous setting or contact your network administrator.

Website Owner Fixes for Slow DNS Lookup

If you own a website, you should not rely on visitors changing DNS settings. You need to optimize your domain, DNS provider, CDN setup, resource loading, and third-party scripts.

1. Use a Reliable Authoritative DNS Provider

Choose a DNS provider with:

• Global anycast DNS
• Strong uptime
• Fast response times
• DNSSEC support
• Easy record management
• Monitoring options
• Reliable support

A slow authoritative DNS provider can affect first-time visitors when records are not already cached.

2. Reduce Third-Party Domains

Audit your site for unnecessary external domains.

Common sources of extra DNS lookups include:

• Ad networks
• Analytics tools
• Heatmap tools
• Chat widgets
• Social media embeds
• Video players
• External fonts
• CDN subdomains
• Payment scripts
• Affiliate scripts

Remove tools that do not provide real value. If a third-party script does not help conversions, revenue, analytics, or security, consider removing it.

3. Shorten CNAME Chains

Long CNAME chains can create extra DNS work. Keep DNS records clean and direct.

Bad example:

www.example.com
→ site.builder.com
→ proxy.platform.net
→ edge.cdnprovider.net
→ final IP

Better example:

www.example.com
→ edge.cdnprovider.net
→ final IP

4. Use Practical TTL Values

Use lower TTL values before migrations and higher values after your setup is stable.

5. Monitor DNS From Multiple Locations

Website owners should not test DNS only from their own device. A domain may resolve quickly in one country but slowly in another region.

Monitor:

• DNS lookup time
• Authoritative DNS response
• Resolver differences
• Region-specific failures
• CNAME chain delays
• DNSSEC errors
• CDN DNS performance

Resource Hints: dns-prefetch vs preconnect

Resource hints help browsers prepare important connections earlier. web.dev explains that resource hints help developers optimize page load time by telling the browser how to load and prioritize resources.

dns-prefetch

dns-prefetch asks the browser to resolve a domain before the resource is needed. MDN explains that DNS prefetch attempts to resolve domain names before resources are requested.

Example:

<link rel="dns-prefetch" href="//cdn.example.com">

Use it for lower-priority external domains that may be needed soon.

Good candidates include:

• CDN domains
• Analytics domains
• Font domains
• Video domains
• Payment tool domains
• Important third-party script domains

preconnect

preconnect starts DNS, TCP, and TLS work earlier for an important origin. web.dev explains that preconnect and dns-prefetch can make applications feel faster by handling connection work ahead of time.

Example:

<link rel="preconnect" href="https://cdn.example.com" crossorigin>

Use preconnect only for critical domains needed early in the page load.

Do not add preconnect for every domain. Too many early connections can waste browser resources and delay more important requests.

Core Web Vitals Connection

Slow DNS lookup is not a Core Web Vitals metric by itself, but it can delay the beginning of the loading process. Google’s Core Web Vitals documentation explains that Core Web Vitals tools measure LCP, INP, and CLS, which represent loading performance, responsiveness, and visual stability.

If your main content, hero image, CSS, font, or JavaScript comes from a third-party domain with slow DNS, your page may start loading later. That delay can indirectly affect user experience and performance scores.

Website owners should check:

• DNS lookup time
• CDN connection time
• TTFB
• LCP element source
• Third-party scripts
• Font loading
• Image optimization
• Server response time

WordPress-Specific Fixes

WordPress websites often become slow because of too many plugins and third-party scripts. DNS lookup problems may appear when a WordPress page loads many external domains for ads, analytics, fonts, social embeds, CDN files, and payment tools.

Check these common DNS-related issues:

• Multiple analytics plugins
• External font requests
• Ad network scripts
• Chat plugins on every page
• Page builder resources
• CDN misconfiguration
• Security plugin DNS lookups
• WooCommerce payment scripts
• Social share buttons
• Embedded videos

Fixes:

• Remove unused plugins
• Use a trusted DNS provider
• Use a CDN correctly
• Reduce external domains
• Host fonts locally when appropriate
• Add preconnect only for critical origins
• Use caching plugins carefully
• Test using Chrome DevTools
• Avoid loading unnecessary scripts sitewide

A WordPress site with fewer external domains is usually easier to optimize and debug.

Troubleshooting Table: Cause, Test and Fix

When You Should Contact Your ISP or Hosting Provider

Contact your ISP when:

• All websites have slow DNS lookup
• All devices on your network are affected
• Restarting the router does not help
• Public DNS works, but ISP DNS fails
• DNS requests frequently time out

Contact Your Hosting Provider If:

• Only your website has slow DNS lookup
• DNS records are incorrect
• Nameservers are not responding
• Website migration caused DNS issues
• Users in some regions cannot access your domain

Before Contacting Support, Collect:

• Chrome DevTools screenshot
• nslookup or dig results
• DNS resolver tested
• Device and network details
• Recent DNS changes

Having this information ready helps support teams diagnose and resolve DNS issues faster.

Common Myths About Slow DNS Lookup

How We Tested and Researched This Guide

This guide was prepared using practical troubleshooting logic and official technical documentation from Google, MDN, Cloudflare, Quad9, Microsoft, Chrome DevTools, Ubuntu manpages, and web.dev. The research focused on DNS lookup behavior, browser timing measurement, TTL, DNS caching, public DNS resolvers, resource hints, and Core Web Vitals.

The testing approach includes:

• Checking DNS timing in browser performance tools
• Comparing DNS resolvers with nslookup
• Comparing public DNS providers against ISP DNS
• Reviewing browser DNS timing using domainLookupStart and domainLookupEnd
• Separating DNS lookup from TTFB and full page load
• Checking TTL and DNS propagation behavior
• Reviewing dns-prefetch and preconnect
• Connecting DNS performance with website speed and user experience

Why DNS Problems Are Often Misdiagnosed

Many users assume slow websites are always caused by poor internet speed or weak hosting. In reality, DNS delays happen before the browser even connects to the server, which means a website can feel slow even when hosting performance is otherwise good. Proper DNS testing helps separate DNS issues from backend, CDN, JavaScript, or server-response problems.

Conclusion

Knowing How to Fix Slow DNS Lookup helps you solve one of the most confusing causes of slow browsing and slow website loading. DNS lookup happens before the browser connects to a website, so delays at this stage can make even a fast internet connection feel slow.

For normal users, the best fixes are to restart the browser, flush DNS cache, restart the router, test another DNS resolver, disable VPN temporarily, and scan for suspicious DNS changes. For website owners, the best solutions are to use a reliable DNS provider, reduce third-party domains, shorten CNAME chains, set practical TTL values, monitor DNS globally, and use resource hints carefully.

The most important rule is simple: test before changing settings. Once you know whether the problem is caused by your browser, device, router, ISP DNS, VPN, or website DNS setup, fixing slow DNS lookup becomes much easier.

FAQs About How to Fix Slow DNS Lookup

1. What is the fastest way to fix slow DNS lookup?

The fastest way to fix slow DNS lookup is to restart your browser, flush DNS cache, restart your router, and test another DNS resolver. If only one website is slow, test that domain with Chrome DevTools, nslookup, or dig.

2. Does changing DNS make internet faster?

Changing DNS does not increase your actual download speed, but it can make websites start loading faster if your current DNS resolver is slow, overloaded, or poorly routed.

3. Why does Chrome stay on “resolving host”?

Chrome may stay on “resolving host” when DNS lookup is delayed. This can happen because of browser cache, OS cache, router DNS, ISP DNS, VPN routing, or a slow authoritative DNS provider.

4. Is slow DNS lookup the same as slow hosting?

No. DNS lookup happens before the browser connects to the server. Slow hosting usually affects TTFB or page rendering after DNS lookup is complete.

5. How do I check DNS lookup time?

You can check DNS lookup time using Chrome DevTools Network timing or browser performance data. A useful measurement is:

domainLookupEnd - domainLookupStart

6. What is the best DNS server for speed?

There is no single best DNS server for every location. Google Public DNS, Cloudflare DNS, Quad9, and ISP DNS can perform differently depending on your country, network, and resolver routing.

7. Can slow DNS lookup affect SEO?

Yes, indirectly. Slow DNS lookup can delay page loading and reduce user experience. It may also affect performance signals if important page resources depend on slow external domains.

8. What is DNS propagation?

DNS propagation is the time it takes for DNS record changes to reach users and resolvers after an update. It is related to TTL and cached DNS records.

9. Should I use dns-prefetch or preconnect?

Use dns-prefetch for lower-priority external domains and preconnect for critical domains needed early. Do not overuse preconnect because unnecessary early connections can waste browser resources.

10. When should I contact my ISP?

Contact your ISP if all websites are slow, all devices are affected, router restart does not help, or ISP DNS fails while public DNS works.

11. Why is only one website slow to resolve?

If only one website has slow DNS lookup, the issue may be related to that domain’s authoritative DNS provider, DNS records, CNAME chain, DNSSEC setup, CDN configuration, or recent DNS changes.

12. Is flushing DNS cache safe?

Yes, flushing DNS cache is generally safe. It removes stored DNS records from your device and forces the system to request fresh DNS information.

Mercy

Mercy is a passionate writer at Startup Editor, covering business, entrepreneurship, technology, fashion, and legal insights. She delivers well-researched, engaging content that empowers startups and professionals. With expertise in market trends and legal frameworks, Mercy simplifies complex topics, providing actionable insights and strategies for business growth and success.

See Full Bio