How To • Networking • DNS Troubleshooting

How to reduce DNS latency for faster browsing

This guide will help you identify if DNS slowness is the cause of laggy web browsing and show you how to switch to faster, more reliable DNS servers. You'll learn to test your current DNS latency, configure new servers on your device or router, and use tools to verify the improvement.

Note: Steps may vary by device and router model. This guide focuses on safe, general methods.

Quick Answer

Run a DNS latency test (like nslookup or a DNS benchmark tool) to see if your current server is slow.
Choose a faster, public DNS service like Cloudflare (1.1.1.1) or Google (8.8.8.8).
Change the DNS server on your device in its network settings.
For a whole-network fix, change the DNS in your router's admin panel.
Flush your device's DNS cache to start using the new servers immediately.
Test browsing speed after the change to confirm improvement.

If this doesn’t work, follow the diagnostic flow below to rule out other network issues like Wi-Fi interference or ISP problems.

What you need

Before you start

A device connected to your network (computer or phone).
Access to your device's network settings.
Your router's admin login details (usually on a sticker).
A basic speed test result to rule out general slow internet.
Admin/sudo privileges if changing settings on a computer.

Good to know

DNS translates website names (like luvvhelp.com) to IP addresses.
Your ISP provides default DNS servers, but they aren't always the fastest.
Public DNS services often offer better speed, security, and reliability.
Changing DNS does not increase your maximum internet bandwidth.
DNS changes are reversible; you can always go back to "Obtain automatically".

Diagnose the issue in 2 minutes

Is it only one device or all devices on your network?
- One device: Likely a device-specific DNS setting or cache issue.
- All devices: Points to a router or ISP DNS problem.
Can you ping an IP address but not a website name?
- Open a command line and try ping 8.8.8.8 (should work).
- Then try ping google.com. If this fails or is slow, DNS is the likely culprit.
Is the problem consistent or intermittent?
- Consistent slowness: Often a poor default DNS server.
- Intermittent timeouts: Could be an unreliable DNS server or network congestion.
Quick Check: Test DNS response time.
- Use a command like nslookup luvvhelp.com and note the response time.
- Times consistently over 100ms indicate room for improvement.

Step-by-step guide

Step 1 — Check your current DNS server

Find out which DNS servers your device is currently using. This is your baseline.

Windows/macOS/Linux: Open a terminal/command prompt and type nslookup or ipconfig /all (Windows) / scutil --dns (macOS) / cat /etc/resolv.conf (Linux).
Router: Log into your router's admin page (often 192.168.1.1) and look under WAN or DNS settings.

What you should see: One or two IP addresses labeled "DNS Servers". These are likely from your ISP.

Step 2 — Test latency to your current and alternative DNS

Measure how fast different DNS servers respond. Lower latency (in milliseconds) is better.

Use a built-in tool like ping on the DNS server IP (e.g., ping 1.1.1.1).
For a more comprehensive test, use free desktop software like DNS Benchmark (for Windows) or dnsspeedtest (cross-platform).
Test well-known public DNS servers: Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9).

What you should see: The public servers often have lower and more consistent ping times than ISP defaults.

Step 3 — Choose a faster DNS service

Based on your tests, pick a primary and secondary DNS server address.

For speed: Cloudflare (1.1.1.1 & 1.0.0.1) often ranks among the fastest.
For reliability/ubiquity: Google DNS (8.8.8.8 & 8.8.4.4).
For security/privacy: Quad9 (9.9.9.9) blocks malicious domains.

What you should see: A decision for a primary (e.g., 1.1.1.1) and backup (e.g., 1.0.0.1) server.

Step 4 — Change DNS on a single device (recommended first)

Apply the new DNS settings to your computer or phone to test the effect.

Windows: Go to Network & Internet Settings > Change adapter options. Right-click your connection > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties. Select "Use the following DNS server addresses" and enter your chosen IPs.

macOS: System Settings > Network. Select your connection, click Details > DNS. Click the + button to add your new DNS server IPs. Drag them to the top of the list.

Linux (GUI): Go to network settings, edit your connection, navigate to the IPv4/IPv6 tab, and switch the DNS method to "Automatic (DHCP) addresses only" or "Manual", then enter the DNS servers.

What you should see: The new DNS addresses saved in your network adapter settings.

Step 5 — Change DNS on your router (for whole network)

To fix DNS for all connected devices (phones, smart TVs, etc.), change it at the source.

Log into your router's admin page via its IP address in a web browser.
Navigate to the WAN, Internet, or DHCP settings section.
Look for a field for "DNS Server" or "Static DNS".
Enter the primary and secondary DNS IPs you selected.
Save settings; the router may reboot.

What you should see: After the router reboots, all devices obtaining IPs via DHCP will use the new DNS.

Step 6 — Flush your device's DNS cache

Clear old, cached DNS entries to force your device to use the new servers immediately.

Windows: Open Command Prompt as Admin and type: ipconfig /flushdns

macOS: Open Terminal and type: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux: The command varies by distribution. For systemd-resolved, use: sudo systemd-resolve --flush-caches

What you should see: A confirmation message like "Successfully flushed the DNS Resolver Cache."

Step 7 — Verify and test the improvement

Confirm the new settings are active and that browsing feels faster.

Run nslookup again to confirm the "Server" line shows your new DNS IP.
Visit several different websites, including ones you haven't visited recently.
Perform another DNS latency test to compare with your initial baseline.

What you should see: Faster initial loading of websites and lower response times in DNS tests.

Common fixes by symptom

Symptom: "Some websites load very slowly, others are fine."

Likely causes: The slow websites might be using a CDN or hosting provider that your ISP's DNS doesn't resolve efficiently. Geographic DNS routing is suboptimal.

Safe fixes: Switch to a global public DNS (Cloudflare, Google). Flush local DNS cache. Check if the problem persists in a different web browser.

When to stop: If switching DNS doesn't help, the slowness may be in the website's server itself.

Symptom: "First website visit is slow, but refresh makes it fast."

Likely causes: Classic sign of high DNS latency. The initial delay is the DNS lookup; the refresh uses the now-cached address.

Safe fixes: Follow the steps in this guide to lower your DNS latency. Ensure your browser's DNS cache isn't being cleared excessively.

When to stop: If the first-visit delay is eliminated after changing DNS.

Symptom: "Connected to Wi-Fi but 'No Internet' or 'Can't find server' errors."

Likely causes: DNS server is completely unreachable or timing out. Could be an incorrect DNS setting or an ISP DNS outage.

Safe fixes: Set DNS to "Obtain automatically" to revert to defaults. If that works, then manually set to a reliable public DNS. Try using your phone as a hotspot to test.

When to stop: If you regain connectivity after changing DNS, the fix worked. If not, the issue may be a broader network disconnection.

Symptom: "High ping spikes in games or video calls only at the start."

Likely causes: The game or app performing a DNS lookup for a matchmaking server or service endpoint during connection setup.

Safe fixes: Use a low-latency DNS. Some gaming routers allow you to prioritize gaming traffic, which can include DNS queries.

When to stop: If the initial connection lag is reduced. Persistent in-game ping spikes are a different issue (packet loss, congestion).

Symptom: "One device is slow, but others on the same network are fine."

Likely causes: Device has hard-coded (manual) DNS settings pointing to a slow/unreachable server. Corrupted DNS cache on that device.

Safe fixes: On the problematic device, change DNS settings to "Obtain automatically" or set to a known-good public DNS. Flush its DNS cache.

When to stop: If the device's performance matches others after the change.

Quick reference

Metric	What it means for DNS	Good Baseline
Latency (Ping)	Time for a DNS server to respond to a query. Lower is better.	< 50ms (local), < 100ms (public)
Jitter	Variation in DNS response times. High jitter causes inconsistent browsing.	As low as possible (< 20ms)
Packet Loss	DNS queries that get no reply, causing timeouts and failed page loads.	0% is ideal. Anything > 1% is problematic.
Throughput	Not typically a concern for DNS, as queries are very small.	N/A
DNS Cache Hit Rate	How often a requested address is already stored locally, avoiding a lookup.	Higher is better. A good cache reduces latency to near zero for repeat visits.

Setting	Safe Baseline	Notes
Primary DNS	1.1.1.1 or 8.8.8.8	Use a reliable, low-latency public service.
Secondary DNS	1.0.0.1 or 8.8.4.4	Provides backup if the primary fails.
Router Admin Access	Strong, unique password	Change from the default to prevent unauthorized changes.
DNS-over-TLS/HTTPS (DoT/DoH)	Enable if supported	Encrypts DNS queries for privacy, may add minimal overhead.
Router Firmware	Keep updated	Updates can improve DNS handling and security.

Mind map summary

Reduce DNS Latency
├── Diagnose
│   ├── Is it all devices or just one?
│   ├── Can you ping IP but not website name? → Yes = DNS issue.
│   └── Test with `nslookup` or DNS benchmark.
├── Solutions (Try in order)
│   ├── On Single Device
│   │   ├── Change DNS in network adapter settings.
│   │   ├── Use Cloudflare (1.1.1.1) or Google (8.8.8.8).
│   │   └── Flush DNS cache (ipconfig /flushdns).
│   └── On Whole Network
│       ├── Change DNS in router admin (WAN/DHCP settings).
│       ├── Router reboot required.
│       └── All DHCP clients get new DNS.
└── Verify
    ├── Confirm new server with `nslookup`.
    ├── Test browsing to new sites.
    └── Re-run latency test.

Troubleshooting checklist

Device

Flush DNS cache.
Change DNS to manual (1.1.1.1 / 1.0.0.1).
Disable VPN temporarily.
Test with a different browser.
Reboot the device.

Router

Log in and check WAN DNS settings.
Change router DNS to public servers.
Update router firmware.
Reboot the router.
Check for DHCP conflicts.

ISP & External

Test during off-peak hours.
Run a general speed test (to rule out bandwidth issues).
Contact ISP to ask about known DNS outages.
Try using your phone's mobile hotspot for comparison.

When to escalate

Contacting your ISP: If changing to multiple reputable public DNS servers does not resolve timeouts or slow browsing, the problem may be with your ISP's routing or connection. Also escalate if you suspect a regional outage affecting multiple users.
Replacing your router: If your router consistently fails to apply DNS settings, crashes after changing them, or is very old (does not support modern DNS features like DoT), consider replacement.
Asking IT support: In a workplace or managed network, do not change router DNS without authorization. If you are on a corporate network and experience DNS issues, report it to your IT department.

What to collect before you escalate

Results of DNS latency tests before and after changes.
General internet speed test results (download/upload/ping).
Timestamps of when the problem occurs.
Specific error messages (e.g., "DNS_PROBE_FINISHED_NO_INTERNET").
Whether the issue affects one device or all devices.

FAQ

Will changing DNS make my internet faster?

It can make web browsing feel faster by reducing the initial delay when looking up a website's address. It does not increase your maximum download/upload speed (bandwidth). If your main slowdown is during large file downloads or video streaming after the initial buffering, DNS is less likely to be the bottleneck.

Is public DNS safe? Will Google or Cloudflare see all my browsing?

Public DNS services from reputable providers like Cloudflare and Google generally have strong privacy policies, often promising not to sell your query data. They can see the domain names you look up, but not the full URL of what you do on that site (if you use HTTPS). Using your ISP's DNS is not necessarily more private; they may also log your activity.

What is the difference between changing DNS on my device vs. my router?

Changing DNS on a single device (like your laptop) only affects that device. Changing it on your router affects every device that gets its network settings from the router (via DHCP), including phones, tablets, and smart home devices. Changing it on the router is more comprehensive.

What are DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH)? Should I use them?

These are protocols that encrypt your DNS queries, preventing others on your network (or your ISP) from seeing which websites you're looking up. They can enhance privacy but may be slightly slower due to encryption overhead. If your router or device supports them and you prioritize privacy, enabling them is a good practice.

Can I use two different DNS services (primary and secondary)?

Yes, the secondary DNS server is used only if the primary fails to respond. It's fine to mix services (e.g., Cloudflare primary, Google secondary), but for consistency, it's often simpler to use the same provider for both.

Why do I have to flush DNS cache? Doesn't it update automatically?

Your device and browser store DNS lookups to speed up repeat visits. When you change DNS servers, old cached entries from the old server are still there. Flushing the cache forces your device to perform fresh lookups using the new servers, ensuring you see the effect immediately.

Could a VPN affect DNS latency?

Yes, absolutely. Most VPNs route all your traffic, including DNS queries, through their own servers. This can increase latency if the VPN server is far away. Some VPNs have their own DNS, which may be faster or slower than your default. If you use a VPN, your device's local DNS settings are often overridden.

How often should I check or change my DNS?

Once you've set up a reliable, fast DNS (like a major public service), you rarely need to change it. You might re-check if you notice a persistent slowdown in browsing, or if you move to a new location where a different provider has lower latency.

Sources and references

Microsoft Windows documentation on TCP/IP and networking commands (ipconfig, nslookup).
Apple macOS support articles on network configuration and DNS management.
Linux man pages for tools like systemd-resolve, dig, and resolv.conf.
General networking concepts from IETF (Internet Engineering Task Force) RFCs on DNS.
Wi-Fi Alliance and IEEE 802.11 standards overviews for underlying network health.
Router vendor administration guides (general concepts for DNS configuration).
Public DNS provider documentation (Cloudflare, Google DNS, Quad9) on usage and benefits.
Networking diagnostics primers covering ping, traceroute, and packet loss.

Menu

How to reduce DNS latency for faster browsing

AI Assistant

Was this tool helpful?