Two days back, I purchased a domain to setup a blog and for that I also purchased a hosting service. I usually don’t host all websites on a single server. After setting up everything like nameserver, installing WordPress, I noticed that I’m unable to open the site.
At first I thought DNS has not been updated because it often takes up to 24 hrs to get updated. A day later, I still couldn’t open the site. Then I noticed that there was no problem on mobile browser. I was facing this problem only on my PC. Then I contacted the hosting company and they also couldn’t help me.
I got frustrated and tried to see what the error is and it was DNS_PROBE_FINISHED_NXDOMAIN. So I searched about it, tried so many things nothing worked. Finally changing default DNS solved my problem. But It’s not necessary that only that solution will work for you as well. So I listed down 9 ways to solve the problem. And I’m confident that you’ll be able to solve the problem. This guide will help you understand what this error is, why it occurs, and how to fix it step-by-step.
What Is DNS_PROBE_FINISHED_NXDOMAIN?
The DNS_PROBE_FINISHED_NXDOMAIN error happens when your browser cannot find the server IP address of the website you’re trying to visit. “DNS” stands for Domain Name System, which translates website names (like example.com) into IP addresses (like 192.0.2.1). “NXDOMAIN” means “Non-Existent Domain,” indicating that the DNS failed to find the domain.
Why Does DNS_PROBE_FINISHED_NXDOMAIN Occur?
Several reasons can cause this error:
- Expired or Unregistered Domain: The domain name might not be active.
- DNS Misconfiguration: Incorrect DNS settings on your device or the server.
- Browser Cache Issues: Outdated DNS information stored in your browser.
- Network Problems: Issues with your internet connection or router.
- Firewall or Antivirus: Security software blocking the website.
- VPN Interference: VPN settings causing connectivity issues.
- CDN Issues: Problems with the content delivery network.
How to Fix DNS_PROBE_FINISHED_NXDOMAIN
Here are nine methods to fix this error:
1. Flush the DNS Cache
Flushing the DNS cache can remove outdated information. Here’s how to do it:
Windows:
- Open the Command Prompt as an administrator.
- Type
ipconfig /flushdns
and press Enter. - Restart your computer.
macOS:
- Open the Terminal application.
- Type
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
and press Return. - Enter your password if prompted and press Return again.
- Restart your computer.
Google Chrome:
- Open Chrome and type
chrome://net-internals/#dns
in the address bar. - Click on “Clear host cache.”
- Restart Chrome.
2. Release and Renew the IP Address
This method clears the old IP address and requests a new one.
Windows:
- Open the Command Prompt as an administrator.
- Type the following commands one by one, pressing Enter after each:
ipconfig /release
ipconfig /renew
- Restart your computer.
macOS:
- Go to System Preferences -> Network.
- Select your current internet connection and click on the “Advanced” button.
- Go to the “TCP/IP” tab and click “Renew DHCP Lease.”
- Restart your computer.
3. Change the DNS Servers
Switching to public DNS servers like Google’s or Cloudflare’s can resolve DNS issues.
Windows:
- Open Control Panel -> Network and Internet -> Network and Sharing Center.
- Click on “Change adapter settings.”
- Right-click your network connection and select “Properties.”
- Select “Internet Protocol Version 4 (TCP/IPv4)” and click “Properties.”
- Choose “Use the following Google Public DNS server addresses” and enter:
- Preferred DNS Server: 8.8.8.8
- Alternate DNS Server: 8.8.4.4
- Click OK and restart your browser.
macOS:
- Open System Preferences -> Network.
- Select your current connection and click “Advanced.”
- Go to the “DNS” tab and click the “+” button.
- Enter 8.8.8.8 and 8.8.4.4 for Google DNS.
- Click OK and restart your browser.
Google Chrome:
- Type
chrome://settings/security
in the address bar. - Scroll down to “Advanced” and select “With Custom.”
- Choose a public DNS like Google or Cloudflare.
- Restart Chrome.
4. Restart the DNS Client Service (Windows Only)
Restarting the DNS client service can resolve DNS issues.
Using Windows System Configuration:
- Press
Windows + R
and typemsconfig
. - Go to the “Services” tab and find “DNS Client.”
- Uncheck the box, click OK, and restart your computer.
- Re-enable the DNS Client service and restart again.
Using Windows Services Manager:
- Open the Services application.
- Find “DNS Client” and click “Restart.”
- Restart your computer.
Using Command Prompt:
- Open Command Prompt as an administrator.
- Type
net stop dnscache
and press Enter. - Type
net start dnscache
and press Enter. - Restart your computer.
5. Check the Local Hosts File
The hosts file can block certain websites. Checking and editing this file might help.
Windows:
- Open Notepad as an administrator.
- Go to File -> Open and navigate to
C:\Windows\System32\drivers\etc\
. - Select “All Files” and open the hosts file.
- Look for any entries with the target website and delete them.
- Save the file and restart your browser.
macOS:
- Open Terminal.
- Type
sudo nano /private/etc/hosts
and press Return. - Enter your password if prompted.
- Remove any entries with the target website.
- Press
Control + O
to save andControl + X
to exit. - Restart your browser.
6. Reset Chrome Flags
Disabling experimental Chrome features can resolve the error.
- Type
chrome://flags
in the address bar. - Click “Reset all” at the top.
- Restart Chrome.
7. Disable Antivirus or VPN
Antivirus or VPN software can sometimes block websites. Temporarily disable them to see if it resolves the issue.
Disabling VPN:
Windows:
- Go to Settings -> Network & Internet -> VPN.
- Select your VPN and click “Disconnect.”
- Restart your computer.
macOS:
- Open System Preferences -> Network.
- Select your VPN connection and click “Disconnect.”
- Restart your computer.
Disabling Antivirus:
Check your antivirus software’s documentation for instructions on temporarily disabling it.
8. Temporarily Turn Off Your CDN
If you own a website and use a CDN, disable it to see if it resolves the error.
Cloudflare:
- Go to the Cloudflare dashboard.
- Scroll down and click “Pause Cloudflare on Site.”
9. Reboot Internet Connection
Restarting your router and modem can fix connectivity issues.
- Unplug both the modem and router.
- Wait for 30 seconds.
- Plug the modem back in and wait for one minute.
- Plug the router back in and wait for two minutes.
- Restart your computer and check the website.
Conclusion
The DNS_PROBE_FINISHED_NXDOMAIN error can be caused by various issues, from DNS misconfigurations to network problems. By following these nine methods, you should be able to resolve the error and regain access to the website. If all else fails, contact your internet service provider or website hosting provider for further assistance.
FAQs
1. What is the DNS_PROBE_FINISHED_NXDOMAIN error?
Answer: The DNS_PROBE_FINISHED_NXDOMAIN error occurs when your web browser cannot resolve the domain name of the website you are trying to visit. Essentially, the Domain Name System (DNS) cannot find the IP address corresponding to the domain name, resulting in an error that prevents you from accessing the website.
2. Why does the DNS_PROBE_FINISHED_NXDOMAIN error occur?
Answer: The DNS_PROBE_FINISHED_NXDOMAIN error can occur for several reasons, including:
- The domain name is expired or unregistered.
- DNS misconfiguration on the user’s computer or device.
- Problems with the internet connection.
- Interference from antivirus software or VPNs.
- Issues with the local hosts file or browser cache.
3. How can I fix the DNS_PROBE_FINISHED_NXDOMAIN error on Windows?
Answer: To fix the DNS_PROBE_FINISHED_NXDOMAIN error on Windows, you can try the following steps:
- Flush the DNS cache using the Command Prompt.
- Release and renew your IP address.
- Change your DNS servers to public DNS (e.g., Google DNS or Cloudflare DNS).
- Restart the DNS client service.
- Check and edit the local hosts file.
- Reset Chrome Flags if using Google Chrome.
- Disable any antivirus software or VPNs temporarily.
- Restart your internet connection by rebooting the router and modem.
4. How do I flush the DNS cache on macOS?
Answer: To flush the DNS cache on macOS, follow these steps:
- Open the Terminal application.
- Enter the command
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
. - Press the Return key and enter your password if prompted.
- Open your browser to check if the error is resolved.
5. Can using a VPN cause the DNS_PROBE_FINISHED_NXDOMAIN error?
Answer: Yes, using a VPN can sometimes cause the DNS_PROBE_FINISHED_NXDOMAIN error. VPNs can interfere with DNS settings, leading to issues in resolving domain names. To check if your VPN is causing the problem, temporarily disable it and see if the error persists. If disabling the VPN resolves the issue, you may need to adjust your VPN settings or contact the VPN provider for further assistance.