
DNS_PROBE_FINISHED_NXDOMAIN means your browser can’t find the website’s address in its DNS records. This typically happens when your internet connection drops, your DNS settings are misconfigured, or the domain has issues. To fix it fast: Restart Chrome, clear your cache, or try flushing your DNS cache using Terminal on Mac.
Also, you will be able to know:
ToggleWhat Does DNS_PROBE_FINISHED_NXDOMAIN Mean?
When you type a website address into Chrome, your computer asks a DNS server “Where is this website?” If that server can’t find the domain name, Chrome shows this error.
Here’s what the technical parts mean:
| Term | Meaning |
|---|---|
| DNS | The system that translates website names (like google.com) into internet addresses |
| PROBE | Chrome checking different DNS servers to locate the domain |
| FINISHED | Chrome completed its search |
| NXDOMAIN | The domain doesn’t exist or can’t be found (Non-Existent Domain) |
Think of it like looking up a phone number in a phonebook that doesn’t have it listed. The search is complete, but the entry doesn’t exist.
Why You’re Seeing This Error
This error appears for three main reasons:
1. Temporary Internet Glitch — Your connection dropped briefly while Chrome tried to reach the DNS server.
2. DNS Cache Problems — Your computer stored old or incorrect information about the website’s address.
3. Domain or DNS Issues — The website’s DNS records might be misconfigured, or the domain registration expired.
Bonus reason: If you’re seeing this on Android devices, it’s usually the same root cause but requires different fixes. We’ll cover those steps below.
How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Mac

Step 1: Restart Chrome (The Quick Fix)
Close Chrome completely and reopen it. This clears temporary data and resets your connection.
How to do it:
- Click the Chrome menu (three dots) in the top right
- Select “Quit Chrome”
- Wait 10 seconds
- Reopen Chrome and try the website again
This fixes the issue about 40% of the time because it resets Chrome’s internal DNS cache.
Step 2: Clear Your Chrome Cache
Cached data can become corrupted and point to incorrect DNS information.
Steps:
- Open Chrome and press Command + Shift + Delete
- Set time range to “All time”
- Check “Cookies and other site data” and “Cached images and files”
- Click “Clear data”
- Refresh the website
Step 3: Flush Your DNS Cache on Mac
Your Mac stores DNS information too. Flushing it forces your computer to get fresh DNS data.
Open Terminal and run this command:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Enter your Mac password when prompted. Your DNS cache will clear immediately.
Note: According to Apple’s technical documentation, this method works on macOS Monterey and newer. For older versions, use slightly different commands.
Step 4: Change Your DNS Server
Your internet provider’s DNS server might be experiencing issues. Switching to Google’s public DNS often resolves this.
To change DNS on Mac:
- Open System Preferences → Network
- Click your active connection (Wi-Fi or Ethernet)
- Click “Advanced” → “DNS”
- Click the “+” button
- Enter 8.8.8.8 and 8.8.4.4 (Google’s DNS servers)
- Click “OK” and “Apply”
Google’s DNS is free, reliable, and used by millions of people worldwide according to their public documentation. Some users also prefer Cloudflare’s DNS (1.1.1.1).
Step 5: Check Your Internet Connection
Sometimes the error is simply a connectivity issue.
Test your connection:
- Restart your Wi-Fi router (turn it off for 30 seconds)
- Try accessing a different website
- Check if other devices can connect to the internet
- If offline, your ISP might be having outages
DNS_PROBE_FINISHED_NXDOMAIN on Android

The error appears identically on Android devices, but the fix is slightly different.
Android solutions:
- Close Chrome completely and reopen it
- Go to Chrome Settings → Privacy and Security → Delete browsing data (select “All time”)
- Turn airplane mode on for 10 seconds, then off again
- Clear your Android system cache: Settings → Apps → Chrome → Storage → Clear Cache
Most Android users find success with these steps because they reset the device’s DNS resolver.
When the Error Isn’t Your Fault
If you’ve completed all steps above and the error persists on multiple websites, the problem likely exists on the website owner’s side.
Signs the website has DNS problems:
- The error appears for you but not for friends on different networks
- The error persists for several hours
- Other people report it on social media
In these cases, contact the website owner and let them know about the issue. Their DNS provider or domain registrar may need to make corrections.
Prevention Tips for the Future
Keep this error from returning:
Stay proactive: Clear your Chrome cache monthly. Go to Chrome Settings → Privacy and Security → Delete browsing data.
Update regularly: Ensure your Mac and Chrome are fully updated. Updates include important DNS and security fixes.
Use reliable DNS: Stick with Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) instead of your ISP’s default DNS.
Monitor connectivity: Use Wi-Fi that’s stable. Move closer to your router or use an Ethernet connection if problems persist.
Actionable Next Steps
If you’re still seeing this error, here’s what to do now:
- Immediately: Restart Chrome and clear your cache using Command + Shift + Delete
- Within 5 minutes: Flush your DNS cache using the Terminal command above
- If still failing: Switch to Google DNS (8.8.8.8) following Step 4
- If persists: Restart your Mac and router completely, then try again
- As a last resort: Contact your Internet Service Provider to ask if there are DNS outages in your area
Most users resolve this error within these five steps. If you’ve tried everything and the issue continues across multiple websites, you may have a deeper connectivity issue that requires ISP support.
Key Takeaways
DNS_PROBE_FINISHED_NXDOMAIN is Chrome’s way of saying “I can’t find this website’s address.” It’s usually temporary and fixable in minutes. Start with the quick fixes (restart Chrome, clear cache), then move to more technical solutions (flush DNS, change DNS servers). Ninety percent of users resolve it without contacting support.
Keep this guide handy for the next time you see this error, you’ll know exactly what to do. If you’re experiencing the broader “DNS probe finished no internet” issue across multiple platforms and situations, check out our comprehensive guide on fixing DNS probe finished no internet errors, which covers solutions for Windows, Android, Mac, and Ubuntu.
Maical is an experienced Network Administrator with a background in the airlines and aviation industry. He specializes in Server Administration, Network Administration, Cisco Networking, IT Hardware Support, and Cisco Router management. Holding an MLIS focused on Information Technology, he also manages several online businesses and web platforms. Maical writes about web hosting, server management, cybersecurity, SEO, and online business based on years of hands-on technical experience.

MUST SEE
-
/ 3 weeks agoHours From Now Calculator: What Time Will It Be? (Free Tool)
Need to know what time it'll be in a few hours or what time...
By Maical -
/ 3 months ago100 Best Books for Beginners Reading (With Links to Buy or Read Free)
The 100 best books for beginners reading, sorted by category, with working links to...
By SLBuddy Team -
/ 3 months ago“Your Organization’s Data Cannot Be Pasted Here”: What It Means and How to Fix It
Seeing "your organization's data cannot be pasted here"? Here's what the Intune error means...
By Maical

