When a client complained that their site kept loading stale assets, the culprit turned out to be their ISP’s DNS cache. Flushing the browser didn’t help because the resolver was still handing out the old IP. I asked them to point the machine at a public resolver, and the page refreshed instantly. That single change saved an afternoon of digging through caching layers.

Below is the exact process I use on every Windows 11 workstation I set up, plus a quick comparison of the three most popular public DNS providers. Stick to the steps, and you’ll avoid the common pitfalls that trip up even seasoned admins.

Why Switch DNS on Windows 11?

Changing the DNS resolver does three things you can see right away:

  • Speed, a fast resolver returns the IP address in fewer milliseconds, shaving time off every request.
  • Reliability, big ISPs sometimes drop queries or return NXDOMAIN for domains that actually exist.
  • Privacy & Security, providers like Cloudflare and Quad9 filter out known malware domains and don’t log your IP.

If you’re on a corporate network that forces a corporate DNS, you might still want a secondary resolver for personal devices. The steps below work whether you’re tweaking a single laptop or rolling the change out via Group Policy.

The Windows 11 UI Method (quickest for a single machine)

  1. Open Settings → Network & internet.
  2. Click Wi-Fi or Ethernet, depending on your connection.
  3. Choose Hardware properties.
  4. Scroll down to DNS server assignment and click Edit.
  5. Switch the toggle to Manual, turn IPv4 on, and paste the primary and secondary DNS addresses.
  6. Hit Save.

Practical warning: If you leave the IPv6 toggle on but don’t provide IPv6 DNS servers, Windows will fall back to the automatically assigned ones, which may undo your change. Either disable IPv6 or enter the provider’s IPv6 addresses as well.

Using PowerShell for Automation

When you need to change DNS on dozens of machines, the UI is too slow. PowerShell gives you a one-liner that works on any network adapter.

Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses "1.1.1.1","1.0.0.1"
  • Set-DnsClientServerAddress, cmdlet that updates the DNS list for a given adapter.
  • -InterfaceAlias "Wi-Fi", replace with the exact name shown in Get-NetAdapter.
  • -ServerAddresses "1.1.1.1","1.0.0.1", primary and secondary DNS; change to the provider you prefer.

Run the script as an administrator. You can pipe a list of adapters from Get-NetAdapter if you want to apply the same servers to every NIC.

Provider Comparison: Cloudflare vs Google vs Quad9

| Feature | Cloudflare (1.1.1.1) | Google (8.8.8.8) | Quad9 (9.9.9.9) | |---|---|---|---| | Performance | Usually the fastest in global ping tests. | Slightly slower in some regions, but still sub-30 ms for most users. | Comparable to Google; a bit slower in Asia. | Privacy | No logs, promises to delete query data within 24 h. | Stores minimal data for troubleshooting; retains IP for a short period. | Logs only aggregated data, no personal IP. | Security | DNS-over-HTTPS/ TLS support, blocks known malware. | Basic DNSSEC validation, no built-in malware block. | Blocks domains flagged by threat intel feeds. | IPv6 | 2606:4700:4700::1111 / ::1001 | 2001:4860:4860::8888 / ::8844 | 2620:fe::fe / ::9

If you value raw speed and a strong privacy promise, Cloudflare is the default. For organizations that already trust Google’s ecosystem, the Google resolver is a safe bet. Quad9 shines when you need an extra layer of threat protection without paying for a premium service.

Verifying the Change

After you’ve updated the settings, open a Command Prompt and run:

nslookup example.com

You should see the resolver IP you just entered in the Server: line. If you still see your ISP’s address, double-check the adapter name and make sure you didn’t leave IPv6 pointing elsewhere.

Another quick test is to visit https://dnschecker.org/ and look at the “Resolver IP” column. It confirms that your queries now travel through the public DNS you chose.

Common Pitfalls and How to Avoid Them

  • Mixed IPv4/IPv6 settings, as noted earlier, leaving IPv6 on with no servers can cause Windows to fall back to the automatic resolver. Always set both stacks or disable IPv6 entirely.
  • Group Policy overrides, on domain-joined machines, a GPO may push DNS settings after you change them manually. In that case, edit the GPO or use a higher-priority policy.
  • Router DNS hijacking, some home routers rewrite DNS queries to their own servers regardless of the client setting. Disable the router’s DNS proxy or set the router itself to use the public DNS you prefer.
  • Cache lingering, Windows caches DNS responses for up to 24 hours. Run ipconfig /flushdns after the change to clear the old entries.

When to Keep Your ISP’s DNS

There are a few scenarios where you might not want to switch:

  • Enterprise split-DNS, internal hostnames (e.g., intranet.corp) are only resolvable via the corporate DNS.
  • Location-based services, some ISPs provide geo-specific DNS responses that improve CDN performance for local content.
  • Metered connections, a few ISPs count DNS queries against your data cap; switching to a free public resolver can actually save you bandwidth.

If any of these apply, consider configuring a secondary resolver (the public DNS) rather than replacing the primary entirely.

FAQ

How do I revert to the original DNS settings?

Open Settings → Network & internet → Hardware properties, edit DNS assignment back to Automatic, or run Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses in PowerShell.

Does changing DNS affect VPN connections?

Most VPN clients push their own DNS servers when the tunnel is active. If you notice DNS leaks, enable the VPN’s “Kill switch” or configure the VPN to use the same public DNS you set locally.

Can I use DNS over HTTPS (DoH) on Windows 11 without third-party software?

Windows 11 includes built-in DoH support, but you need to enable it via Settings → Network & internet → Advanced network settings → DNS → Enable DNS over HTTPS and paste the provider’s DoH URL (e.g., https://cloudflare-dns.com/dns-query).

Wrapping up

If you ever find yourself chasing stale content or slow page loads, the first place to look is the resolver. Switching to a fast, privacy-focused DNS on Windows 11 is a single-click change in the UI, a one-line PowerShell command for automation, and it pays off instantly. Pick the provider that matches your priorities—speed, privacy, or security—and you’ll notice the difference right away.