# How to Fix DNS Errors in the Windows 11 Edge Browser
When you open a website in Microsoft Edge on Windows 11 and the page refuses to load, the browser often surfaces a **DNS error** instead of the site you expected. These errors are common, they are rarely caused by malware, and in most cases you can fix them in a few minutes. This guide explains what each DNS error code means, why it happens in the latest versions of Edge and Chrome, and walks through four practical solutions you can apply right now.
## The DNS Error Codes You Will See in Edge
Edge (and Chrome, since both share the same underlying engine) typically displays one of three error strings when domain name resolution fails:
– **`dns_probe_finished_nxdomain`** — The domain name could not be resolved. The DNS server was asked for an IP address and returned no result, meaning it could not find the requested domain.
– **`dns_probe_finished_no_internet`** — The browser could not reach a DNS server at all, which usually points to a broader connectivity problem rather than a single bad domain.
– **`dns_probe_started`** — A DNS query was initiated but never completed. This usually indicates a timeout or an interrupted lookup rather than a hard failure.
Any of the three can appear intermittently or persistently, and they often affect every site you try to visit rather than just one.
## Why Modern Edge and Chrome Trigger DNS Errors
Recent versions of Microsoft Edge and Google Chrome ship with **Secure DNS** enabled by default. Secure DNS, also known as **DNS-over-HTTPS (DoH)**, encrypts your DNS queries by sending them through an HTTPS tunnel instead of plain-text UDP packets. This improves privacy, but it also introduces a new failure mode: if anything along the path does not support encrypted DNS, lookups break silently.
The most common culprits are:
– **Router incompatibility.** Many home and small-office routers have built-in DNS relays that were designed for traditional, unencrypted DNS. When the browser tries to push DoH traffic through them, the request is dropped.
– **ISP or carrier filtering.** Some internet service providers inspect or restrict traffic they cannot classify. HTTPS-wrapped DNS packets can be flagged and blocked by network policy.
– **Unstable or geo-restricted public DNS endpoints.** The default DoH resolvers baked into Edge and Chrome may have slow, unreliable, or regionally blocked entry points. If the resolver is unreachable, every lookup fails.
The result is the same regardless of cause: Edge cannot translate a domain name into an IP address, and you see a DNS error page.
## Solution 1: Switch to a Different Browser
The fastest way to confirm that the problem is DNS-specific is to try another browser. Install or open **Firefox**, **Microsoft Edge Dev**, or another browser that does not force Secure DNS on by default.
– If websites load normally in the alternate browser, you have confirmed the issue is Edge’s DNS configuration, not your internet connection.
– If every browser fails, move on to the router-level fixes below, because the problem is further down the network stack.
This is a diagnostic step as much as a workaround. It isolates the fault quickly and tells you where to focus your effort.
## Solution 2: Change Your Router’s DNS Settings (Recommended for Home and Office Networks)
The most thorough fix is to configure a reliable public DNS server directly on your router. This overrides the DNS settings for every device on your local network at once, so phones, tablets, and laptops all benefit.
1. **Log in to your router’s admin panel.** Open a browser and enter the router’s IP address in the address bar. Common addresses are `192.168.1.1` or `192.168.0.1`. Enter the admin username and password — the defaults are usually printed on a label on the back or bottom of the router.
2. **Locate the DNS settings.** Look under sections labeled **Network Settings**, **Advanced Settings**, **WAN**, or **DHCP Server** for a field called “DNS Server.”
3. **Enter a public DNS provider.** A widely used, stable option is Alibaba Cloud’s public DNS:
– **Primary DNS:** `223.5.5.5`
– **Secondary DNS:** `223.6.6.6`
These addresses are optimized for fast response times and high availability.
4. **Save the configuration and reboot the router.** Most routers require a restart before the new DNS settings take effect. Power-cycle the device, wait for it to reconnect, and test Edge again.
Because this change happens at the router level, it resolves DNS errors for every device on the network in a single step.
## Solution 3: Customize Secure DNS (DoH) in Edge or Chrome
If you want to keep the privacy benefits of encrypted DNS, you can point Edge or Chrome at a DoH resolver that works reliably on your network instead of disabling the feature entirely.
### Edge Browser
1. Open Edge and type `edge://settings/privacy` in the address bar to reach the **Privacy, Search, and Services** page.
2. Scroll to the **Security** section and find the **Use secure DNS** toggle.
3. Select **Choose a service provider** (or **Custom provider**) and enter one of the following DoH endpoints:
– Alibaba Cloud DoH: `https://dns.alidns.com/dns-query`
– Tencent Public DoH: `https://doh.pub/dns-query`
4. If Edge reports that the server is unreachable, try an alternate endpoint:
– Cloudflare DoH: `https://doh.cloudflare-dns.com/dns-query`
– Google DoH: `https://dns.google/dns-query`
Note that Cloudflare and Google endpoints may require unrestricted internet access and can be blocked on some networks.
### Chrome Browser
1. Open Chrome and go to `chrome://settings/privacy` to open the **Privacy and Security** page.
2. Click **Security**, then find **Use secure DNS**.
3. Choose **With (Custom)** as the provider and paste the same DoH address you selected for Edge.
4. Save and reload the page that was failing.
Custom DoH gives you encrypted lookups without depending on whatever default resolver the browser picked, which is often the source of the error in the first place.
## Solution 4: Flush the Local DNS Cache and Check for Interference
Even after you change DNS servers, stale entries in Windows’ local cache can keep sending the browser to a bad result. Clearing the cache forces fresh lookups through your newly configured server.
1. **Flush the DNS cache.** Click the Start button, type `cmd`, right-click **Command Prompt**, and select **Run as administrator**. At the prompt, type:
“`
ipconfig /flushdns
“`
Press Enter. You should see a confirmation that the resolver cache was flushed.
2. **Temporarily disable third-party security software.** Some antivirus suites and personal firewalls inspect outbound traffic and can mistakenly block DNS queries, including DoH. Try disabling the software briefly (or adding an exception for the browser process) and reload the page.
3. **Verify the DoH endpoint is actually reachable.** If you pasted `https://dns.alidns.com/dns-query` or `https://doh.pub/dns-query` into Edge and still see errors, the service itself may be experiencing a temporary outage. Wait a few minutes, or switch to a backup endpoint such as `https://doh.aliyun.com/dns-query`.
## Summary: Which Fix Should You Try First?
– **Start with Solution 2 (router DNS).** Changing the DNS server at the router level is the most reliable fix because it resolves the problem for every device and every browser on the network at once.
– **Use Solution 3 (custom DoH) if you need encrypted DNS.** Pick a DoH provider known to work on your network and check its status periodically, since public endpoints can have intermittent outages.
– **Keep Solution 4 (flush and verify) in your toolkit.** Even after a configuration change, flushing the Windows DNS cache eliminates leftover bad entries.
– **Watch for browser updates.** Microsoft and Google periodically expand their built-in lists of DoH providers and improve compatibility. Keeping Edge and Chrome current can prevent the issue from recurring.
> **Recency and risk note:** DNS resolver endpoints, browser settings pages, and router admin interfaces change over time. The specific IP addresses and DoH URLs listed above were accurate as of the original publication date. Always verify that a public DNS provider is operational before relying on it, and avoid entering credentials into any web page that does not match your router’s expected admin interface.
