How to Change DNS Server on Windows for Faster Browsing

What if the reason a browser feels sluggish has nothing to do with the internet plan, the router, or even the device itself? Our team has spent years troubleshooting slow and unreliable connections, and one fix keeps surfacing that most people completely overlook: DNS. Knowing how to change DNS server on Windows is a fast, free optimization that anyone can apply in under five minutes — no technical background required. This guide, part of our broader tech tips series, covers everything from the fundamentals to side-by-side provider comparisons.

DNS — short for Domain Name System — acts as the internet's phonebook. Every time a browser loads a page, it first consults a DNS server to translate a site name (like palmgear.com) into a numerical IP address. The default servers assigned by most ISPs (Internet Service Providers) are functional, but they are frequently overloaded and can be geographically distant, which adds small but measurable delays to every page load. Swapping to a faster public resolver is consistently one of the highest-value tweaks in our networking toolkit.

Anyone who wants to confirm their current network settings before making changes will find our guide on how to find your IP address on Windows a practical first stop — it helps ensure the right adapter is being configured. For households managing multiple devices on the same network, our walkthrough on how to share files between two Windows computers on a network pairs naturally with this one.

DNS Fundamentals: What Home Users and Power Users Both Need to Know

The Basics in Plain Terms

Most people interact with DNS dozens of times a day without realizing it. Type a web address, press Enter, and before anything loads, Windows queries a DNS server. That server looks up the corresponding IP address — a string of numbers like 142.250.80.46 — and hands it back so the browser knows where to connect. The entire exchange happens in milliseconds, but the quality of the DNS server determines how fast those milliseconds pass.

ISP-assigned DNS servers prioritize broad compatibility over raw speed. Our team has measured lookup times on default ISP servers running 80–120 milliseconds, while well-optimized public alternatives often settle under 20 milliseconds. Over hundreds of daily lookups, that gap accumulates into a noticeably snappier browsing experience. According to Wikipedia's overview of the Domain Name System, the infrastructure is decades old — but the servers people connect to vary enormously in real-world performance.

Pro tip: Our team always tests DNS changes with a free tool like DNS Benchmark before committing — the fastest server on paper isn't always the fastest for a specific geographic location.

Where Power Users Take It Further

Beyond basic speed, advanced users choose DNS providers for additional features: built-in malware blocking, family content filters, and DNS-over-HTTPS (DoH — an encrypted DNS protocol that prevents ISPs from monitoring browsing queries). Cloudflare's 1.1.1.1 and NextDNS are popular among privacy-conscious users precisely because they deliver these layers without requiring additional software. Our team has deployed NextDNS on test machines to block tracking domains at the DNS level — the reduction in background network noise is measurable and consistent.

Keeping network drivers current is an often-missed companion step. Our guide on how to update device drivers in Windows covers that process thoroughly — outdated network adapter drivers can quietly undermine the gains from a faster DNS server.

How to Change DNS Server on Windows, Step by Step

Changing DNS on Windows 10

The most reliable method on Windows 10 runs through Network Adapter Settings. Open the Start menu and search for "View network connections," then press Enter. The Network Connections window shows all available adapters — right-click the active one (usually labeled "Ethernet" or "Wi-Fi") and select Properties. In the list that appears, click "Internet Protocol Version 4 (TCP/IPv4)" and then click the Properties button. Select "Use the following DNS server addresses" and enter the preferred and alternate server addresses. Click OK, then OK again to close both dialogs.

For most home users, Google's public DNS (8.8.8.8 and 8.8.4.4) or Cloudflare's 1.1.1.1 and 1.0.0.1 are solid starting points. Flush the DNS cache afterward by opening Command Prompt and running ipconfig /flushdns — this forces Windows to use the new servers immediately rather than drawing on cached lookups tied to the old ones.

Changing DNS on Windows 11

Windows 11 introduced a redesigned Settings path. Open Settings, navigate to Network & Internet, then click the active connection — either Ethernet or Wi-Fi. Select "Hardware properties," scroll down to the DNS server assignment row, and click Edit. Change the dropdown from "Automatic (DHCP)" to "Manual," toggle on IPv4, and enter the preferred and alternate DNS addresses. Save the changes, then flush the cache with the same ipconfig /flushdns command in an elevated Command Prompt (right-click Command Prompt and choose "Run as administrator").

Note: Our team always records the original ISP DNS addresses before switching — writing them down takes ten seconds and makes reverting effortless if anything behaves unexpectedly after the change.

Using Command Prompt for Speed

Power users can skip the GUI entirely. Open an elevated Command Prompt and run these two commands, replacing "Wi-Fi" with the actual adapter name shown by netsh interface show interface:

• netsh interface ip set dns "Wi-Fi" static 1.1.1.1
• netsh interface ip add dns "Wi-Fi" 1.0.0.1 index=2

This method is especially practical when configuring multiple machines, since the commands can be batched into a script and run silently. Our team deploys this approach on lab setups where clicking through GUI dialogs on every machine would be impractical. Anyone documenting the process for a team may find our post on how to record a screen on Windows for free useful for capturing the steps cleanly.

DNS Myths That Keep Home Networks Running Slow

Myth: ISP DNS Is Already Fast Enough

This is the most persistent misconception our team encounters. The assumption is that since the ISP's server is local, it must be fast. In practice, ISP DNS infrastructure is shared across thousands of subscribers, underfunded compared to dedicated public resolvers, and sometimes subject to query logging that adds overhead. Independent benchmarks consistently show Cloudflare and Google DNS outperforming the majority of ISP resolvers in real-world lookup times. "Fast enough" is a low bar — there is no reason to settle when demonstrably better options are free.

Anyone who has already tried standard network fixes — like the steps in our post on how to find a WiFi password on Windows to confirm a device is on the correct network — and still sees slow browsing will often find DNS to be the remaining variable.

Myth: DNS Changes Improve Download Speed

DNS affects lookup time, not bandwidth. Once a connection to a server is established, the DNS server plays no further role in transfer speed. Home users sometimes change DNS expecting faster downloads and notice no difference — because download speed depends entirely on the ISP plan and destination server capacity. The real benefit is reduced latency (connection delay) at page load initiation. Sites that load assets from many different domains — each requiring its own DNS lookup — show the most dramatic improvement. Complex dashboards and media-heavy pages are better examples than a single large file download.

Public DNS Providers Compared Side by Side

How to Read the Numbers

DNS performance is measured in lookup latency — the time in milliseconds between a query and a response. Lower is better. Our team's experience aligns with published benchmarks: Cloudflare 1.1.1.1 consistently leads on raw speed globally, Google 8.8.8.8 offers reliability backed by massive infrastructure, and OpenDNS adds content filtering useful for family environments. The table below summarizes the options that matter most for home and small-office use.

Our Team's Pick

For most home users, Cloudflare 1.1.1.1 is the first choice our team recommends — fast, privacy-respecting, and with an excellent uptime record. Google 8.8.8.8 is the dependable fallback when broad compatibility matters above all else. Households with children get strong value from OpenDNS Family Shield (208.67.222.123 and 208.67.220.123), which blocks adult content at the network level without any software installation. Security-focused home networks benefit most from Quad9, which actively intercepts queries to known malicious domains before a connection is even attempted.

Frequently Asked Questions

Final Thoughts

Switching to a faster public DNS server takes under five minutes on any Windows machine and delivers immediate results across every browser and app that reaches the internet. Our team recommends starting with Cloudflare 1.1.1.1, running a quick nslookup test to confirm the change is active, and treating this as the first adjustment before exploring deeper network optimizations. Anyone working through a broader Windows performance checklist will find this change consistently delivers the fastest return on effort of any network tweak in our experience — make it the first step, not the last.