All about DNS_PROBE_FINISHED_ NXDOMAIN: Fixes and insights

Is your website suddenly unreachable? The DNS_PROBE_FINISHED_NXDOMAIN error can prevent visitors from accessing your site, impacting your traffic and business. 

While this common DNS lookup failure can be frustrating, don’t worry – this comprehensive guide will show you how to identify and resolve various domain resolution issues to keep your website accessible.

Understanding the DNS_PROBE_FINISHED_NXDOMAIN error

When your browser displays the DNS_PROBE_FINISHED_NXDOMAIN message, you’re experiencing a DNS error that prevents proper domain resolution. The Domain Name System (DNS) typically acts as an internet directory, connecting human-readable domain names (like www.example.com) to their corresponding IP addresses. When this system encounters problems, it results in a DNS lookup failure, making websites inaccessible.

When the DNS system can’t find the IP address for a requested domain name, it returns an NXDOMAIN response, indicating the domain doesn’t exist. This prevents access to the website and can significantly impact both users trying to access essential services and businesses relying on their online presence.

How to identify DNS_PROBE_FINISHED_NXDOMAIN errors

Recognizing the DNS_PROBE_FINISHED_NXDOMAIN error is relatively straightforward. Here are some signs that you may be dealing with this issue:

• Website accessibility: If you cannot access a specific website, but other websites load without issue, this error could be the culprit. This suggests that the problem lies with the DNS resolution for that particular domain.
• Error message: The browser will typically display an error message, but it can vary slightly depending on your browser. For instance, Chrome users will see “This site can’t be reached” followed by “dns_probe_finished_nxdomain.” Firefox users will see “Hmm. We’re having trouble finding that site.” followed by “We can’t connect to the server at [website].”
• DNS settings review: If you’ve checked your DNS settings and found no apparent issues, yet you’re still unable to access certain websites, this error might be the cause.
• Network diagnostic tools: Using network diagnostic tools, like the network troubleshooter available on your operating system, can help confirm if you’re dealing with this error. If there’s a problem with the DNS, the tool will highlight it.

Step-by-step solutions to fix the error

Follow these solutions in order, starting with the simplest fixes before moving to more complex ones:

1. Restart your computer and router

A simple restart of the computer and router can often resolve the error. This process resets your network hardware and can often clear up any temporary issues affecting your DNS resolution.

2. Clear browser cache and cookies

Browser cache and cookies can sometimes cause conflicts with DNS resolution. Clearing them can help resolve the DNS_PROBE_FINISHED_NXDOMAIN error. 

Here’s how to do it from a Chrome browser:

1. Click on the three dots in the top right corner of your browser.
2. Click on Settings.
3. On the left, click on Privacy and security.
4. Click on Clear browsing data.
5. Check all three boxes to clear the browsing history, cookies and other site data, and cached images and files, then click the Clear data button. Make sure to change the time range to All time.

The steps to clear cache and cookies on other browsers, like Firefox and Safari, are very similar.

3. Reset Chrome flags

Chrome’s experimental features (flags) can sometimes interfere with proper DNS resolution. Here’s how to reset them:

1. Type chrome://flags in your address bar.
2. Click the Reset all button in the top-right corner.
3. Restart Chrome to apply the changes.

4. Check and change your DNS settings

Correct DNS settings are essential for proper domain name resolution. Here’s how to check and update your DNS settings on Windows, macOS, and Linux:

Windows

1. Open the Control Panel. 
2. Click on Network and Internet.
3. Click on Network and Sharing Center.
4. On the left pane, click on Change adapter settings.
5. Right-click the network interface connected to the Internet (Wi-Fi or Ethernet), and select Properties.
6. Select Internet Protocol Version 4 (TCP/IPv4) and Internet Protocol Version 6 (TCP/IPv6) and then click on Properties. Check that both Obtain an IP address automatically and Obtain DNS server address automatically options are selected.
7. Alternatively, you can select the Use the following DNS server addresses option and enter the address of the DNS server you’d like to use, then click “OK.”

macOS

1. Open System Preferences.
2. Click on Network.
3. Select your network connection from the left panel (Wi-Fi or Ethernet).
4. Click on the Advanced button.
5. Go to the DNS tab, where the DNS servers will be listed in the DNS servers box.
6. To add a new DNS server, click on the + button and add the IP address of the DNS server you want to use.
7. To remove a DNS server, select the IP address you want to remove and then click –.

Linux

1. Open the terminal.
2. Display the contents of the resolv.conf file, which is a configuration file used by the DNS resolver in Linux-based systems, by running the following command:

cat /etc/path_to_resolv.conf_file

3. Edit the resolv.conf file with a text editor to add the DNS server addresses you want to use. For example, you can execute the following to open the resolv.conf file with the nano text editor:

sudo nano /etc/path_to_resolv.conf_file

4. Look for the line that starts with #DNS= and remove the # symbol at the beginning if it’s there.
5. Add your DNS server addresses separated by a space. There are three approaches to this step (change 8.8.8.8 and 8.8.4.4 to the DNS server addresses you want to use:

• For newer versions (using systemd-resolved):

DNS=8.8.8.8 8.8.4.4

• If you’re running an older Linux version, add a line for each DNS server you want to use using the nameserver directive. For example: 

nameserver 8.8.8.8

• For recent versions of CentOS and Fedora, NetworkManager might be managing the DNS configuration. In that case, you should use NetworkManager’s configuration instead of directly modifying /etc/resolv.conf. You can use the nmcli command-line tool to manage NetworkManager settings:

sudo nmcli connection modify <connection-name> ipv4.dns "8.8.8.8 8.8.4.4"sudo nmcli connection up <connection-name>

Replace <connection-name> with the name of your active network connection (either Ethernet or Wi-Fi).

5. Restart DNS client service

If changing DNS settings doesn’t work, try restarting the DNS client service:

Windows

1. Press Windows + R.
2. Type services.msc and press Enter.
3. Find DNS Client in the list.
4. Right-click and select Restart.

macOS

1. Open Terminal.
2. Enter: sudo killall -HUP mDNSResponder.
3. Enter your password when prompted.

Linux

1. Open Terminal.
2. Enter: sudo systemctl restart systemd-resolved. 

6. Disable VPN or antivirus temporarily

If you’re using a VPN or have active antivirus software, you may want to temporarily disable them to see if they’re causing the DNS_PROBE_FINISHED_NXDOMAIN error. The process may vary depending on your operating system, but the general steps are:

To disable your VPN: 

1. Click or right-click the VPN service icon in your system tray (bottom-right or top-right).
2. Most VPN services have a disconnect or stop option in the right-click context menu. If this isn’t the case, you may need to access the settings within the VPN application itself.
3. Click on the option to disconnect or stop the VPN service.

To disable your antivirus software: 

1. Find the antivirus icon in your system tray.
2. Right-click the antivirus icon.
3. In the context menu, look for options like disable, quit, stop, or something similar. If these options aren’t available, you may need to open the antivirus software dashboard to disable it.

5. Check your hosts file

The hosts file plays a key role in DNS resolution. If this file is misconfigured, it can cause the DNS_PROBE_FINISHED_NXDOMAIN error. To check the local hosts file and rule out any issues related to it, follow these steps:

1. Open the “hosts” file on your computer:
2. For Windows, the file is located at C:\Windows\System32\drivers\etc\hosts. You’ll need administrative privileges to modify this file.
3. For macOS and Linux, the file is located at /etc/hosts. You’ll need root privileges to modify it.
4. Look for any entries related to the domain you are trying to access. If you find an entry that maps the domain name to an IP address, it could be causing the issue. You can remove or comment out (by adding a # before the entry) the line to revert to a DNS-based resolution for that domain.
5. Save the changes (if any) to the hosts file.

6. Reset your network configuration

Resetting the network configuration can often help resolve the DNS_PROBE_FINISHED_NXDOMAIN error by clearing any incorrect settings. Here’s how to reset your network configuration on Windows, macOS, and Linux:

Windows

1. Run the Command Prompt as an administrator.
2. Type the following commands one after the other and press Enter after each one:

netsh winsock reset

netsh int ip reset

ipconfig /release

ipconfig /renew

ipconfig /flushdns

3. Close the Command Prompt and restart your computer.

macOS

1. Click on the Apple menu and go to System Preferences.
2. Click on Network.
3. Choose your active network connection (like Wi-Fi or Ethernet) from the list and click the Advanced button.
4. Click on the TCP/IP tab.
5. Select the Renew DHCP Lease button.
6. Click on the DNS tab.
7. Select the + sign to add a DNS and type in 8.8.8.8 and 8.8.4.4 (Google’s DNS).
8. Click on OK and then Apply to save your changes.

Linux (Ubuntu) 

1. Open the terminal.
2. Type the following commands one after the other and press Enter after each one:

sudo systemctl stop NetworkManagersudo systemctl stop systemd-networkdsudo systemctl stop systemd-resolvedsudo systemctl disable NetworkManagersudo systemctl disable systemd-networkdsudo systemctl disable systemd-resolvedsudo apt-get install --reinstall network-manager network-manager-gnomesudo apt-get purge nplan netplan.iosudo rm -f /etc/netplan/*.yamlsudo rm -f /etc/netplan/*.ymlsudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.confsudo systemctl enable NetworkManagersudo systemctl start NetworkManager

sudo dhclient

3. Flush DNS (like on Windows) by installing nscd (Name Service Cache Daemon):

sudo apt-get install nscd
sudo /etc/init.d/nscd restart

4. Incorrect network settings can lead to a loss of internet connectivity. If you’re unsure about any of these steps, it’s recommended to consult with someone experienced with network settings, like Liquid Web’s team of experts. Otherwise, proceed with caution. 

Browser-specific error guides

Different browsers display the DNS_PROBE_FINISHED_NXDOMAIN error in unique ways. Here’s how to resolve this issue in your preferred browser:

Google Chrome

When Chrome shows “This site can’t be reached” with a DNS_PROBE_FINISHED_NXDOMAIN error, follow these steps:

1. Enter chrome://net-internals/#dns in your address bar.
2. Click the Clear host cache button.

Mozilla Firefox

For Firefox, try this solution: 

1. Enter about:networking#dns in the address bar.
2. Click the Clear DNS Cache button.

Microsoft Edge

If Edge shows “Hmmm… can’t reach this page,” follow these steps:

1. Enter edge://net-internals/#dns in the address bar. 
2. Click the Clear host cache button. 

Safari

For Safari users experiencing DNS issues:

1. Open System Preferences (or System Settings).
2. Click Network > Advanced.
3. Select the DNS tab.
4. Click + to add Google’s DNS servers:
   1. Primary: 8.8.8.8
   2. Secondary: 8.8.4.4

5. Click OK, then Apply. 

Get started with Liquid Web’s VPS hosting solutions

When visitors encounter the DNS_PROBE_FINISHED_NXDOMAIN error, they can’t access your website – a critical issue for any online business. This error appears when the DNS system can’t match your domain name to its IP address.

Liquid Web, a leading player in the web hosting industry, offers solutions to prevent and resolve DNS-related issues through:

• Managed hosting services with expert DNS management.
• 99.999 percent uptime guarantee backed by reliable infrastructure.
• 24/7 expert support for quick resolution of DNS issues.
• Flexible hosting options including VPS, dedicated, and cloud dedicated servers.
• One-click scaling to maintain site availability during traffic spikes.
• Custom solutions for complex DNS configurations.

Whether you’re a growing startup or an established enterprise, Liquid Web’s comprehensive hosting solutions and expert support team ensure your website remains accessible and error-free. Don’t miss out on this opportunity to enhance your online presence and ensure your website’s success. Explore Liquid Web’s VPS hosting plans and sign up now!

Related Resources

Expert Tips for Managing Your Own VPS

Managed VPS vs Unmanaged VPS: What’s the Difference?

What Does DNS Do and How Does It Work?

5 simple steps to host your own website in 2024

What is a WordPress pingback?

What is bare metal provisioning?