sodcalculator

10 Tech How-To

Fix DNS Probe Finished NXDOMAIN in Edge

Guide 10-25858 · Updated · Step by step

This error appears when Microsoft Edge cannot find the website’s address because the Domain Name System (DNS) lookup fails. It usually means the browser can’t translate the site name into an IP address. The fixes below range from simple page refreshes to clearing the DNS cache and changing your DNS server, and most take under two minutes.

What You’ll Need

  • Access to your Windows, macOS, or Linux computer where Edge is installed
  • Administrator rights on the computer (for some steps like flushing DNS)
  • Your router’s login details if you need to restart it (usually not required)

Step-by-Step

  1. Check the URL and try again. A typo in the domain name is the most common cause. Verify the spelling, especially the extension (.com, .net, .org). If you copied the link, paste it into a text editor first to see the full address.
  2. Refresh the page. Press F5 or Ctrl+R (Windows/Linux) or Cmd+R (Mac). Sometimes the DNS server returns a temporary failure that resolves on the next request.
  3. Try a different browser or device. Open the same URL in Chrome, Firefox, or your phone’s browser. If it works there, the problem is isolated to Edge or your computer’s network stack. If it fails everywhere, the issue is likely with the website itself or your network.
  4. Restart your router and modem. Unplug both devices, wait 30 seconds, plug the modem back in, wait for it to fully boot, then plug in the router. This clears the router’s internal DNS cache and often fixes temporary network glitches.
  5. Clear the DNS cache on your computer. This removes old, incorrect DNS records that Windows or macOS stores locally.
    • Windows: Open Command Prompt as Administrator (search “cmd”, right-click, “Run as administrator”). Type ipconfig /flushdns and press Enter.
    • macOS: Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder then press Enter. You may need to enter your password.
  6. Reset the network stack (Windows only). In the same Administrator Command Prompt, run these three commands one at a time, pressing Enter after each:
    • netsh winsock reset
    • netsh int ip reset
    • ipconfig /release then ipconfig /renew

    Restart your computer after this.

  7. Change your DNS server to a public one. Your Internet Service Provider’s DNS might be unreliable. Using a public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8) is a common permanent fix.
    • Windows: Go to Settings > Network & Internet > Wi-Fi (or Ethernet) > Hardware properties > Edit next to DNS server assignment. Choose Manual, turn on IPv4, and set Preferred DNS to 1.1.1.1 and Alternate to 1.0.0.1 (or 8.8.8.8 and 8.8.4.4). Save.
    • macOS: System Settings > Network > your connection > Details > DNS. Click the + and add 1.1.1.1 and 1.0.0.1. Click OK.
  8. Disable Edge’s built-in DNS feature. Edge has a setting called “Secure DNS” that can sometimes cause this error. Go to Edge’s Settings (three dots top right) > Privacy, search, and services > Security. Scroll to “Use secure DNS” and turn it off. Reload the page.
  9. Turn off your VPN or proxy. If you use a VPN or a proxy extension, temporarily disable it. These can intercept DNS requests and fail. If the site loads after disabling, the VPN is the problem.
  10. Check your hosts file (advanced). On Windows, the file is at C:\Windows\System32\drivers\etc\hosts. On macOS, it’s /etc/hosts. Open it with Notepad or TextEdit as administrator and look for any line containing the domain name that’s failing. If you see one, add a # at the start of that line to comment it out, save, and try again.

Common Mistakes

  • Forgetting to restart after network resets. The netsh commands and DNS flush often require a reboot to take full effect.
  • Changing DNS on the wrong adapter. If you’re on Wi-Fi, you must change the DNS on the Wi-Fi adapter, not the Ethernet one. Check which connection is active.
  • Typing the wrong command. A single typo in ipconfig /flushdns (like a missing space) will just show an error. Copy-paste the commands from this guide.
  • Assuming the website is down. The error often appears when the site itself is offline. Check a site like “downforeveryoneorjustme.com” before making changes to your system.
  • Disabling secure DNS permanently without testing. Try it, reload the page, and if it works, you can leave it off. But if the issue was temporary, you might want to turn it back on for privacy.

Tips

  • Use a reliable public DNS. Cloudflare (1.1.1.1) and Google (8.8.8.8) are fast and have high uptime. They often resolve sites that your ISP’s DNS cannot.
  • Keep your router’s firmware updated. An outdated router can have DNS bugs. Check the manufacturer’s website for updates.
  • Test with a different domain. If google.com loads but your specific site doesn’t, the problem is likely with that site’s DNS records, not your computer.
  • Use Edge’s “Reload in Internet Explorer mode” as a temporary workaround (Settings > Default browser > Allow sites to be reloaded in Internet Explorer mode). This uses a different network stack and can bypass the error for legacy sites.
  • Consider a browser extension that lets you switch DNS per-site, but only after you’ve tried the system-level fixes above.

Troubleshooting

If you’ve tried all the steps and still see the error, work through this checklist:

  • Is it just one site? If yes, the website’s DNS configuration is likely broken. Wait a few hours and try again. You can also use a public DNS checker (like dnschecker.org) to see if the site’s DNS is propagated globally.
  • Does it happen in private browsing? Open an InPrivate window (Ctrl+Shift+N). If the site loads there, a browser extension or cached data is the culprit. Clear your browsing data (Settings > Privacy > Clear browsing data) and disable extensions one by one.
  • Is your system date and time correct? Incorrect time settings can break SSL certificates and DNS security features. Check your clock settings and enable automatic time sync.
  • Try a different network. Connect your computer to your phone’s mobile hotspot. If the site loads, the problem is with your home network or router, not Edge or your computer.
  • Run Windows Network Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters > Network Adapter > Run. It can sometimes detect and fix issues automatically.
  • If nothing works, reset Edge. Go to Edge’s Settings > Reset settings > Restore settings to their default values. This will remove extensions and reset preferences, but keeps your bookmarks and history. Try the site again after.

Frequently Asked Questions

Q: What does “DNS probe finished NXDOMAIN” actually mean?
A: It means the DNS server responded that the domain name does not exist (NXDOMAIN = Non-Existent Domain). This could be because the site is mistyped, the site’s DNS records are gone, or your DNS server has outdated information.

Q: Will changing my DNS server fix this permanently?
A: It fixes it if your ISP’s DNS is the problem. Public DNS servers like 1.1.1.1 are more reliable and update faster, so this is a common permanent solution for recurring NXDOMAIN errors.

Q: Is this error a sign of a virus or malware?
A: Rarely. A malicious program can alter your DNS settings to redirect you, but the NXDOMAIN error itself is usually a network or configuration issue. If you suspect malware, run a full scan with Windows Defender or your antivirus.

Q: Why does the error happen on one device but not another on the same Wi-Fi?
A: Each device has its own DNS cache and network settings. The failing device might have a corrupted cache or a manual DNS setting that’s wrong. Follow the steps to flush DNS and check your adapter’s DNS settings on that specific device.

Q: Does clearing the browser cache help with this error?
A: It can help if the error is caused by a corrupted cached DNS entry in the browser itself. It’s worth trying, but the system-level DNS flush (step 5) is usually more effective.

Q: Can this error happen because the website is down?
A: Yes. If the website’s owner lets their domain registration lapse or their DNS hosting fails, the domain will return NXDOMAIN for everyone. Check the site from another device or a web-based DNS checker to confirm it’s not just you.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →