The “DNS_PROBE_FINISHED_NXDOMAIN” error can happen on any browser and it could be Chrome, Chromium, Firefox, Edge, Safari, and others. We cannot blame one program for the error because it is a common problem that occurs on any macOS machine. We are going to provide solutions that will help the macOS administrators to solve the “DNS PROBE FINISHED NXDOMAIN” error.
Let’s look at the browser error code and find out whether it matches your problem, so you can be sure of it.
Users have the right to know why this is happening in the machine because you don’t want to end up with multiple wrong conclusions. There is a higher chance of blaming the macOS or system itself that could end up in frustration and waste time.
The website that you are trying to access might be offline or the browser believes that it is offline or does not exist. Remember, the site may not be down and this is happening on your PC only, which might be the case. Many users can access almost every site in the bookmark except for one particular portal and you are welcomed by DNS_PROBE_FINISHED_NXDOMAIN error.
Chrome users are more prone to face the error, when compared to Safari, Firefox, Edge, and other browser users. A site is a combination of the domain name and IP address and that’s where the DNS comes in handy. The DNS (1) or DNS (2) is unable to find the site IP address, which triggers the error on the Chrome browser.
One error has multiple contributing meanings behind it and we are going to solve the error by applying multiple solutions.
A quick shutdown will clear the temporary files in the macOS, and it will remove the hindering files that are causing the errors.
- Tap on the Apple logo > Shutdown.
- Let the MacBook or iMac shutdown.
Wait for two minutes after shutdown and then power up the machine later.
Clear Browsing Data
97% of the Chrome users have a minimum of 1GB saved form data like passwords, cache, cookies, browsing history, site data, and more. The users need to remove saved form data because it piles up old files of a site. Let us assume that iTechCliq old files are saved in your browser, but our team has updated a few files, but Chrome is not able to pick them up. You will have the DNS error on the screen because the Chrome browser is not able to use the old files anymore.
Note: You will lose browsing data and saved passwords in the process until or unless you have signed-in to your Google account. You won’t lose saved bookmarks in the toolbar and the folder.
- Open Chrome and click on the three-dotted setting.
- Choose “Settings” and tap on “Clear browsing data” under “Privacy & Security.”
- Choose “Advanced” and select “All time” under “Time Range”.
- Select all options and then tap on “Clear data” to finish the process.
Chrome takes less than ten seconds to finish the cleaning and restart the macOS machine to start a new session.
Clear DNS Cache
Apple macOS saves cache during the session and it does not delete it until or unless it is required. The terminal is added to the machine for the users because you can use commands to override the macOS functions.
- Go to applications and click to expand “Utilities.”
- Open the “Terminal” app.
- Copy & paste “sudo dscacheutil -flushcache” command and press enter button.
- Copy & paste “sudo killall -HUP mDNSResponder” command and press enter button.
Flush DNS Cache in Chrome
We have used Terminal to clear the DNS cache in macOS and we should clean the DNS cache in the Chrome browser as well.
- Open the Chrome browser.
- Copy & paste “chrome://net-internals/#DNS” command and press enter to access the options.
- Click on “DNS” to access the options.
- Click on “Clear host cache” to finish the process.
Let Chrome clean the DNS cache in the browser and it will take less than ten seconds to do so. However, you won’t get any notification or confirmation pop-up and wait for ten seconds and then close the window.
Now, you can solve “DNS_PROBE_FINISHED_NXDOMAIN” in macOS or Mac computer. If none of the solutions are working then we recommend the users to try Safari in Private Mode because it does not save any data in the browser.