How to Change Your DNS Server on Windows for Faster Internet

According to data published by Cloudflare, the average DNS resolver provided by most internet service providers responds in over 100 milliseconds, meaning every webpage you open carries hidden latency before a single byte of content loads. If you have been wondering how to change your DNS server on Windows, you are already ahead of the majority of users who accept their ISP's default configuration without a second thought. A faster DNS resolver translates directly into snappier browsing, quicker application connections, and a noticeably more responsive network experience. For a broader set of Windows performance guides, browse our tech tips category.

The Domain Name System acts as the internet's phone book, translating human-readable addresses like palmgear.com into the numerical IP addresses that computers use to communicate. When you type a URL into your browser, your machine consults a DNS server before connecting to the destination, and the speed of that lookup affects every single page load you experience. Switching from your ISP's default resolver to a high-performance public option like Google's 8.8.8.8 or Cloudflare's 1.1.1.1 takes under five minutes but delivers results you notice immediately. If you are already comfortable navigating Windows networking, you may want to first check your current IP address on Windows before diving into DNS configuration.

This guide walks you through every method available on Windows, from the graphical settings panel that any beginner can navigate to the command-line approach preferred by power users and network administrators alike.

What Most People Get Wrong About DNS

DNS Does Not Encrypt Your Traffic by Default

A widespread misconception holds that switching to a privacy-focused DNS resolver automatically encrypts all of your internet traffic, but standard DNS queries travel in plain text over UDP port 53, fully visible to anyone positioned between your device and the resolver. Services like Cloudflare's 1.1.1.1 offer DNS-over-HTTPS and DNS-over-TLS as optional configurations, which do encrypt the lookup itself, but they leave the rest of your connection unaffected by design. If full encryption is your goal, a VPN remains the appropriate tool, while a fast DNS resolver remains the appropriate tool for reducing lookup latency. According to Wikipedia's article on the Domain Name System, the protocol was designed in the early 1980s with performance and scalability as primary objectives — not privacy.

Switching DNS encrypts your lookups only if you specifically enable DNS-over-HTTPS; standard DNS queries remain unencrypted regardless of which resolver you choose.

Changing DNS Does Not Bypass Your ISP Entirely

Another persistent myth suggests that a different DNS server routes your traffic through a separate network, effectively hiding your activity from your internet service provider. Your ISP still handles every packet you send and receive; DNS is only the lookup layer, not the data-transport layer, and your browsing history, download volumes, and connection destinations remain visible to your provider through other means even after you change your DNS server on Windows. What the change accomplishes is reducing your dependence on your ISP's often slower and occasionally unreliable resolver infrastructure, which is a meaningful and measurable benefit in itself.

Step-by-Step: How to Change Your DNS Server on Windows

Changing DNS via Network Settings (Beginner Method)

The graphical method works identically across Windows 10 and Windows 11 and requires no technical background to complete. Open the Start menu, type "Network Connections," and select "View network connections" from the results. Right-click the adapter you are currently using — either your Wi-Fi connection or your Ethernet adapter — and choose "Properties" from the context menu. Scroll down until you find "Internet Protocol Version 4 (TCP/IPv4)," double-click it, and select "Use the following DNS server addresses." Enter your preferred DNS in the first field and your alternate DNS in the second, then click OK and close all windows.

For Google's public DNS, use 8.8.8.8 as preferred and 8.8.4.4 as alternate. For Cloudflare's resolver, use 1.1.1.1 as preferred and 1.0.0.1 as alternate. If you also want to update your IPv6 DNS, repeat the process for "Internet Protocol Version 6 (TCP/IPv6)" using the corresponding IPv6 addresses provided by your chosen resolver.

Always configure both a preferred and an alternate DNS server so that your connection falls back gracefully if the primary resolver experiences an outage.

Using Command Prompt or PowerShell (Advanced Method)

Power users and network administrators often prefer setting DNS through the command line because it allows bulk configuration across multiple adapters and supports scripting for repeated deployments across many machines. Open an elevated Command Prompt or PowerShell window by right-clicking the Start button and selecting "Windows Terminal (Admin)" or "Command Prompt (Admin)." To set DNS on your primary adapter, run netsh interface ip set dns "Wi-Fi" static 1.1.1.1, replacing "Wi-Fi" with your adapter's exact name and 1.1.1.1 with your chosen primary resolver. Add a secondary server by running netsh interface ip add dns "Wi-Fi" 1.0.0.1 index=2, then flush your DNS cache immediately with ipconfig /flushdns so the system begins using the new resolver without delay.

If you manage more than one Windows machine on a shared network, applying DNS changes from a single administrative workstation pairs well with the techniques covered in our guide on how to share files between two Windows computers on a network.

Free vs. Paid DNS: A Clear-Eyed Comparison

The Top Free Public DNS Resolvers

The free public DNS ecosystem is dominated by a small number of well-resourced operators whose performance consistently exceeds what residential ISPs provide. The table below compares the most widely used options across the metrics that matter most to everyday users making the decision of how to change their DNS server on Windows.

When a Premium DNS Service Makes Sense

Paid DNS services such as NextDNS or Cisco Umbrella offer granular filtering, detailed query logs, and enterprise-grade uptime guarantees that go well beyond what free resolvers provide. For households where restricting content access is a priority, a service like NextDNS allows you to block specific categories at the DNS level, functioning as a network-wide complement to the tools described in our guide on how to set up parental controls on Windows. Pricing typically ranges from free for limited query volumes to roughly $20 per month for unlimited business-tier plans, a negligible cost against the added administrative control you gain across every device on your network.

Getting More from Your DNS Change

Testing DNS Speed After You Switch

Changing your DNS server on Windows without benchmarking the result leaves you without any baseline for comparison and no confirmation that the change delivered improvement for your specific location. Use the free tool DNS Benchmark by Gibson Research Corporation or the open-source tool namebench to measure your new resolver's actual response time from your geographic region, since performance varies considerably by location and by time of day. Run each test at least three times and average the results to account for network variability before drawing any conclusions about which resolver serves your connection best.

Run your DNS speed test from your actual machine rather than trusting published averages — resolver performance varies significantly by geographic location and local network conditions.

Combining DNS with Other Windows Optimizations

A faster DNS resolver delivers its greatest benefit when combined with other Windows networking and performance improvements that reduce competing system load. Eliminating unnecessary startup programs, for instance, reduces the CPU contention that can delay DNS cache initialization at boot — a process covered in detail in our guide on how to disable startup programs on Windows to speed up boot. You can further reduce redundant DNS lookup volume by confirming that your browser's built-in DNS prefetch feature is active, which pre-resolves domain names for links visible on the current page before you click them.

Long-Term DNS Health: What to Check and When

Signs Your DNS Settings Have Reverted

Windows resets custom DNS settings after major operating system updates, network adapter driver reinstallations, or changes to your router's DHCP configuration that push new DNS assignments to connected devices automatically. You notice the reversion when pages that loaded quickly begin lagging again, or when your benchmark results show response times climbing back toward ISP-level latency without any other obvious cause. Verify your current DNS settings any time your connection feels sluggish by revisiting the Network Connections panel or running nslookup in Command Prompt to confirm which resolver is actively answering your queries.

Periodic Checks That Keep Your Connection Sharp

Routine maintenance of your DNS configuration takes less than five minutes and catches reversion issues before they degrade your experience for days unnoticed. Once a month, open Command Prompt and run ipconfig /all to confirm your DNS server addresses match the ones you originally configured, then flush the cache with ipconfig /flushdns to clear any stale or corrupted entries that have accumulated over time. If you manage multiple Windows devices on the same network, our walkthrough on how to find saved WiFi passwords on Windows offers related techniques for auditing your full network configuration in a single session.

Frequently Asked Questions

Your DNS server is the first handshake your computer makes with the internet — upgrading it costs nothing and changes everything about how fast the web feels.