Subnet Mask Cheat SheetRecords Cheat SheetGeoDNS ExplainedFree Network TroubleshooterKnowledge BasePricing CalculatorLive CDN PerformanceVideo Demos
BlogsNewsPress ReleasesIT NewsTutorials
Give us your email and we'll send you the good stuff.
Heather Oliver is a Technical Writer for Constellix and DNS Made Easy, subsidiaries of Tiggee LLC. She’s fascinated by technology and loves adding a little spark to complex topics. Want to connect? Find her on LinkedIn.
Everyone has likely experienced a webpage error in some way shape or form. I could probably write a novel’s worth of material just trying to explain them all (don’t hold your breath for that one!). But there is one particular domain error that pops up more often than most:
No internet? What do you mean I have no internet? My computer says I have internet … what gives? Can you tell I’ve been here a few times? ¯\_(ツ)_/¯ In certain situations, this error can make the most composed adult want to throw a full-blown tantrum.
But before you let it get that far, check out these tips!
Any time you get a DNS_Probe_finished_No_Internet error, it means that your DNS server can’t load a website or access the web—hence the temptation to throw a tantrum.
This usually happens due to bad DNS settings or a slow internet connection on the user side, or a DNS misconfiguration or propagation issue on the server-side. As annoying as this can be, the good thing is, it’s usually an easy fix.
So, let’s get to fixin’!
Here are a few ways that you can go about solving this problem, both for users and domain administrators. Feel free to skip to the fix most relevant to your situation.
If you’re on the IT side of things, you know an error like this can generate lots of tickets and support calls when users can’t access your domain but can others. When this happens, it’s likely due to one of three culprits: a DNS misconfiguration error, DNS propagation issues, or a time to live (TTL) problem.
Do a propagation test. Using a free tool like Constellix’s DNS Tool Box lets you query records for your domain. This can help pinpoint issues and allow you to run a test to see if your recent DNS updates have propagated across all servers. If the results are unexpected, you know you have some troubleshooting to do.
Check your DNS records and make sure there are no typos or wrongly attributed IP/host addresses. If there was an error, keep in mind that the old information will still be cached in devices and DNS servers until the TTL for the offending record has expired.
If you’ve corrected any misconfigurations and are still experiencing issues after 48 hours, or if there were no DNS-related errors on your side, it’s possible that the problem is on the registrar level. In this case, you’ll need to investigate potential issues at your domain’s registrar.
Being proactive is better than being reactive. Advanced planning can do wonders for preventing IT-related downtime. Prior to making any IP/host updates, lower the TTL values for that record for faster propagation times. This will help you to avoid DNS errors that are a result of caching issues.
These fixes are geared toward end users or issues unrelated to the domain itself. Keep in mind that if you are only having problems accessing one particular website, this is most likely a problem with the company’s own website or their provider. If that’s the case, you’ll have to be patient and wait until the situation is corrected.
If you aren’t able to access the internet at all, despite being “connected,” try the following tips:
While possible to see this error when using any browser, it’s been reported that it’s especially common for Google Chrome users across operating systems. So if you’re a Chrome user, try accessing the website in question (or any website) with a different browser first. That will at least let you know if it’s a browser issue.
If you can access the website from a different browser, follow these steps:
Enter this URL: chrome://flags/
This will take you to Chrome’s Experiments page. At the top right, press the Reset all button.
Next, click Relaunch at the bottom of the screen and try to access the website again. If you are able to access the site, you’re good to go.
If you use another browser besides Chrome, or if Resetting Google flags didn’t solve the problem, try resetting the Winsock Program. While this may sound intimidating, it’s really not!
First, access the Windows Command Prompt by clicking on the search icon in your taskbar. Next, type “command prompt” or “cmd.” This should put the app at the top of the search window under “Best options.”
Make sure the Command Prompt option is highlighted, and then click the option to Run as Administrator to the right.
In the command window, type: netsh winsock reset
Once the process is complete, restart your computer.
If none of the above have helped, try flushing/renewing your device’s DNS settings.
At the command prompt type the following commands, making sure to press enter after each command line (a process will run after each):
Once you’ve run the final command, restart your computer.
To Flush your DNS cache on Mac, follow the steps below:
Open the terminal by using Spotlight Search or by pressing Command + Space and then type Terminal. Double click the application icon for Terminal to open it.
Type: sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder Enter your Mac’s password
Press Enter to complete
After using this command in Mac, you’ll be brought to a new command line.
If you’re a user, hopefully, you’re now “spinning the web” like Spider-Man! If you’re troubleshooting on the server-side because of a DNS no internet error, you should have at least narrowed down whether the problem with your domain is from propagation issues due to TTL or caching, identified and corrected any misconfiguration errors in your DNS records, or have discovered an issue with your registrar.
Sign up for news and offers from Constellix and DNS Made Easy