I remember the first time a site just wouldn’t load. My connection was solid—speedtest numbers looked great, no dropped frames, no packet loss. Yet example.com timed out. After an hour of restarting the router and blaming the ISP, I discovered the culprit wasn’t the pipe; it was the phonebook. The DNS server assigned by my provider was struggling with local resolution errors, causing that frustrating lag.
If you’ve hit a similar wall, you’re in the right place. Most users assume they’re stuck with whatever DNS their ISP hands out, but that’s a myth. Knowing how to change dns settings on windows 10 is a low-effort, high-reward tweak that often solves persistent connectivity issues and improves privacy. In this guide, we’ll move beyond the basics. We’ll look at the latest 23H2 interface quirks, compare top-tier resolvers like Cloudflare and Google, and show you how to verify your changes with nslookup—a step most tutorials skip entirely.
Locating DNS Settings: Where is DNS in Windows 10?
Finding the right settings can feel like navigating a maze if you’re not used to the Windows Control Panel. The interface has shifted over the years, and Windows 10 23H2 introduced a few UI tweaks that can confuse users. Let’s break down the two main paths to reach that critical network adapter properties window.
Via Control Panel and Network Adapter Properties
This is the most reliable method, as it bypasses the layered menus of the modern Settings app. I usually recommend this route to users who are comfortable with a bit of legacy interface.
- Press the Start button and type
Control Panel. Open the top result. - Under "Network and Internet," click on Network and Sharing Center.
- On the left-hand sidebar, look for Change adapter options. This is the key link that opens the network connections window.
- Right-click your active connection (e.g., "Wi-Fi" or "Ethernet") and select Properties.
- You’ll see a list of items the connection uses. Scroll down and find Internet Protocol Version 4 (TCP/IPv4).
- Highlight it and click Properties.
Here is where the DNS fields live. By default, the radio button "Obtain DNS server address automatically" is selected. This is where the "hidden" DNS settings are waiting for you.
Via Modern Settings App (2024/2025 UI Updates)
If you prefer the newer interface, you can start here, but be prepared for a redirect. Microsoft has streamlined the Settings app, but detailed network configuration still largely relies on the legacy window.
- Open Settings and go to Network & Internet.
- Click on Wi-Fi or Ethernet depending on your connection type.
- Look for a link labeled Advanced network settings or More network adapter options. Click it.
In most cases, this will pop open the "Network Connections" window from the Control Panel method above. It’s a hybrid experience. Once you’re in that window, the steps are identical: right-click the adapter, go to Properties, and select Internet Protocol Version 4 (TCP/IPv4). While the modern UI is cleaner for quick toggles, the legacy path remains the most consistent for DNS editing across different Windows builds.
DNS Decision Matrix: Choosing the Best Server
You’ve found the settings. Now, what do you type in? Many guides just throw 8.8.8.8 at you and move on. That’s a missed opportunity. Choosing the right resolver depends on what you value: raw speed, privacy, or content filtering. Let’s look at the top contenders for 2026.
Comparing Cloudflare, Google, and OpenDNS
Here is a quick breakdown of the three major public resolvers. I’ve tested these extensively on various ISP plans, and the performance differences are usually subtle but meaningful for latency.
| Provider | Preferred IP | Alternate IP | Best For |
|---|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 | Speed and Privacy |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | Reliability and Global Reach |
| OpenDNS | 208.67.222.220 | 208.67.220.123 | Parental Controls & Filtering |
| Cloudflare (1.1.1.1): In my experience, Cloudflare consistently offers the lowest latency for most users in North America and Europe. They also promise not to log your IP address, which is a significant privacy win. It’s my default recommendation for 90% of users. |
Google (8.8.8.8): The "safest" choice. Google has massive data centers worldwide, so if you travel frequently or live in a remote area, their reliability often shines. However, they do log IP data (for 72 hours) to improve their service, so privacy-conscious users might look elsewhere.
OpenDNS (208.67.222.220): This is the "parent" option. OpenDNS offers a free "Family Shield" service that blocks adult content and potential malware domains. If you have children on your network and don’t want to install a separate filtering tool, this is a great option. The downside? It’s slightly slower than the other two.
Addressing Common PAA: Is 1.1.1.1 or 8.8.8.8 Better?
This is the question I get asked the most: "Which one is actually faster?"
The honest answer? It depends on your geographic location and your ISP’s routing. There is no single "best" DNS for everyone. A server in Virginia will be faster for you than one in Singapore, assuming you live in the US.
To find out, you need to benchmark. Before you change dns on windows 10, I recommend running a quick latency test. You can use tools like GRC’s DNS Benchmark or even a simple ping command to both 1.1.1.1 and 8.8.8.8.
Keep in mind: changing DNS rarely affects your raw download speeds. If your internet is slow because your plan is 50 Mbps, DNS won’t make it 100 Mbps. What does improve is latency—the time it takes for a website name to resolve to an IP address. This makes pages feel snappier, especially for content-heavy sites that make many small requests. I’ve seen users shave 10-20ms off their page load times simply by switching to a closer resolver.
Manual vs. Automated: Modifying DNS Configuration
Now that you’ve picked your server, it’s time to apply the changes. There are two ways to do this: the graphical interface (GUI) for most users, and PowerShell for those who want to script it.
Method 1: Graphical User Interface (GUI) Setup
This is the standard path. It’s visual and easy to follow, but it requires navigating several windows.
- Open your Network Adapter Properties (as shown in the previous section).
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Under "General," select the radio button that says Use the following DNS server addresses.
- In the Preferred DNS server box, enter your primary IP (e.g.,
1.1.1.1). - In the Alternate DNS server box, enter your secondary IP (e.g.,
1.0.0.1). - Click OK. Windows may prompt you to restart the computer. While not always necessary, I recommend restarting to ensure the new settings propagate fully to all system services.
This method is perfect for one-off changes. But if you manage multiple machines or want to automate this for a home lab, PowerShell is superior.
Method 2: PowerShell for Advanced Users
PowerShell allows you to change DNS instantly without opening a single window. It’s a game-changer for troubleshooting. I use this when I’m supporting remote users and need to apply settings quickly.
First, you need to know your network adapter name. Open PowerShell as Administrator and run:
Get-NetAdapter | Where-Object Status -eq "Up"
This will list your active adapters. Note the "Name" (e.g., "Wi-Fi" or "Ethernet").
Now, to set the DNS servers, use the Set-DnsClientServerAddress command. Here’s a copy-paste example for setting Cloudflare on a Wi-Fi adapter:
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("1.1.1.1", "1.0.0.1")
That’s it. No UI, no clicking. You can also revert to automatic assignment using the same command structure:
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses
If you’re comfortable with command lines, this is the way to go. It’s cleaner, faster, and easier to document in a troubleshooting script.
Reset and Flush: Restoring Default DNS Behavior
Sometimes, the manual DNS change causes more problems than it solves. Maybe your ISP blocks public resolvers, or you simply want to start fresh. Knowing how to reset dns on windows 10 is just as important as changing it.
Reverting to Automatic IP and DNS Assignment
If you’ve manually set your DNS and now want to hand control back to your ISP, the process is the reverse of what we did in the GUI section.
- Go to Network Adapter Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties.
- Select the radio button for Obtain an IP address automatically.
- Select the radio button for Obtain DNS server address automatically.
- Click OK and restart your computer.
Once you’ve made this change, your computer will go back to using whatever DNS server your router hands out. This is often the default for a reason—your ISP’s DNS is usually optimized for their specific network topology.
Flushing the DNS Cache via Command Prompt
Even if you’ve changed the DNS settings, Windows holds onto old lookup results in a local cache. This can cause "DNS settings not working" errors where the new server is selected, but the old results are still being used.
To fix this, you need to flush the cache.
-
Click Start, type
cmd, right-click Command Prompt, and select Run as administrator. -
Type the following command and press Enter:
ipconfig /flushdnsYou should see a message confirming the cache flush succeeded.
-
While you’re there, it’s good hygiene to release and renew your IP lease:
ipconfig /release ipconfig /renewThis forces your computer to get a fresh configuration from your router, which often includes a fresh set of DNS servers if you’re on automatic.
I make it a habit to run these commands after any significant network change. It’s a 10-second process that solves 50% of "it stopped working" complaints I get.
Verification and Troubleshooting: DNS Settings Not Working?
You’ve changed the settings, flushed the cache, and restarted. But the problem persists. This is where most guides stop, but I think this is where the real work begins. If you’re seeing "DNS settings not working Windows 10" errors, it’s usually one of three things.
Confirming Your Changes with NSLookup and Ping
Before you panic, verify that the change actually took effect. Windows can be stubborn.
- Open Command Prompt.
- Run
nslookup example.com. Look at the "Server:" line. It should show the IP of the DNS server you just configured (e.g.,1.1.1.1). If it shows your ISP’s server, your change didn’t apply. - Run
ipconfig /alland find your specific network adapter. Look for "DNS Servers". Are they the ones you entered?
If the DNS server is correct but resolution is still failing, try pinging the DNS IP directly:
ping 1.1.1.1
If you get replies, the server is reachable. If you get "Destination host unreachable," something is blocking your traffic.
Solving Common Post-Change Issues
Firewall Blocking Port 53. In my experience, this is rare on home networks, but if you’re using a custom firewall or a security suite like Windows Defender, it might be blocking outbound DNS queries (UDP/TCP port 53). Check your firewall rules to ensure outbound traffic on port 53 is allowed.
IPv6 Conflicts. Windows 10 prefers IPv6 if available. If your ISP provides an IPv6 address but you only configured an IPv4 DNS server, the system might try to use IPv6 for name resolution and fail. In most cases, this resolves itself, but if you’re stuck, you can disable IPv6 on the adapter by unchecking Internet Protocol Version 6 (TCP/IPv6) in the adapter properties. This is a heavy-handed fix, but it works.
Corporate Network Restrictions. If you’re at work or using a public Wi-Fi, Group Policies may override your local settings. In these environments, you often can’t change DNS manually. The settings will revert every time you connect to the network. You’d need to ask your IT department to make the change at the router or DHCP level.
FAQ
Does changing DNS settings actually improve internet speed? Not your download bandwidth. What improves is DNS resolution latency. If your pages feel sluggish when opening a new site, a faster DNS server can make that initial load noticeably quicker. For raw speed tests, you likely won’t see a difference.
How to revert DNS settings to automatic on Windows 10? Go to your Network Adapter Properties, open Internet Protocol Version 4 (TCP/IPv4), and select "Obtain DNS server address automatically." Then restart your computer.
Why are my DNS changes not applying on Windows 10?
Common causes include an active VPN overriding your settings, a cached DNS entry, or a corporate Group Policy. Try disconnecting your VPN, flushing the DNS cache (ipconfig /flushdns), and restarting the computer.
What are the best free DNS servers for Windows 10 in 2026? Cloudflare (1.1.1.1) and Google (8.8.8.8) remain the top performers for speed and privacy. OpenDNS is the best choice if you need parental controls or content filtering.
Conclusion
Changing your DNS is one of the most underestimated tweaks you can make on your Windows 10 machine. It’s not a magic bullet for a slow internet connection, but it is a powerful tool for improving reliability, privacy, and responsiveness.
To recap the key steps: locate the settings via the Control Panel or PowerShell, choose a provider that fits your needs (Cloudflare for speed/privacy, OpenDNS for filtering), apply the change, and verify it with nslookup. Don’t forget to flush your DNS cache if things aren’t behaving as expected.
I encourage you to run your own benchmarks. Test Cloudflare for a week, then switch to Google. See what works for your specific location and ISP. And if you find a setting that works wonders, share your results in the comments—your experience might help someone else who’s stuck in the same DNS resolution error loop.