- Home
- Knowledge Base
- Networking
- How Do I Fix “DNS Probe Finished No Internet”…
How Do I Fix “DNS Probe Finished No Internet” on Chrome?
“To fix the ‘DNS_PROBE_FINISHED_NO_INTERNET’ error in Chrome, check your internet connection, restart your router, disable problematic VPN or proxy settings temporarily, clear the DNS cache, and verify your device’s DNS configuration.”
The DNS_PROBE_FINISHED_NO_INTERNET error in Google Chrome usually indicates that Chrome cannot complete the required network or DNS resolution process to reach a website.
DNS, or Domain Name System, translates domain names such as example.com into IP addresses. The error can result from connectivity issues, DNS configuration problems, router issues, VPN or proxy settings, or temporary service disruptions.
The steps below apply primarily to Windows computers. Menu names may vary by operating system and Chrome version.
How to Fix the DNS Probe Finished No Internet Error
Step 1: Check Your Internet Connection
First, determine whether the problem affects one website or your entire connection.
- Open a few different websites.
- Check whether other devices on the same Wi-Fi network can access the internet.
- If all devices are affected, restart your router or modem.
- If only one device is affected, continue with device-level troubleshooting.
Step 2: Restart Chrome and Your Router
- Close and reopen Chrome.
- Restart your computer if needed.
- Power-cycle your router or modem using the manufacturer’s instructions.
- Reconnect to the network and test the website again.
Step 3: Disable VPN or Proxy Temporarily
A misconfigured VPN or proxy can interfere with DNS resolution.
- Disconnect the VPN temporarily if your organization’s policies allow it.
- Check your system’s proxy settings.
- Test the connection again.
If you are using a company-managed device or VPN, consult your IT administrator before changing required settings.
Step 4: Clear the Windows DNS Cache
On Windows:
- Open Command Prompt.
- Run Command Prompt as administrator if required.
- Enter the following command:
ipconfig /flushdns
- Press Enter.
- Reopen Chrome and test the website.
This clears the local DNS resolver cache. It does not change your DNS server configuration.
Step 5: Renew the IP Address
If the device has an IP configuration problem, try the following commands in an elevated Command Prompt:
ipconfig /release
ipconfig /renew
The first command releases the current IPv4 configuration, and the second requests a new one. Your connection may briefly disconnect while this happens.
Step 6: Check DNS Server Settings
If the problem continues, check whether your device is using a valid DNS server.
You may be able to use a trusted public DNS resolver, such as Google Public DNS or Cloudflare DNS, if permitted by your network policy.
For business-managed devices, do not replace organization-required DNS settings without approval. Internal DNS may be necessary for company applications, domain services, or security controls.
Step 7: Check Chrome’s Secure DNS Setting
Chrome supports Secure DNS, which can affect how domain lookups are handled.
- Open Chrome settings.
- Search for Secure DNS.
- Review the current setting and provider.
- If appropriate, test another supported configuration or temporarily turn the feature off to isolate the issue.
Follow your organization’s policies on managed browsers and DNS security.
Step 8: Update Chrome and Check Network Drivers
If the error persists:
- Update Chrome.
- Check for network adapter driver updates.
- Review firewall or security software logs.
- Test the connection on another network, if appropriate.
Avoid disabling your firewall or antivirus as a routine troubleshooting step.
Quick Troubleshooting Guide
| Symptom | Possible Cause | What to Check |
| All devices have no internet | Router or ISP issue | Router status and internet service |
| Only one computer is affected | Device configuration | DNS, IP settings, network adapter |
| Websites fail only when VPN is connected | VPN or DNS routing issue | VPN configuration and assigned DNS |
| Only internal company sites fail | Internal DNS or access issue | Corporate DNS and network policies |
| Only one website fails | Website or domain-specific issue | Try another network and check the domain |
Final Thoughts
The DNS_PROBE_FINISHED_NO_INTERNET error is often caused by connectivity or DNS configuration issues. Start with the simplest checks and proceed to DNS and IP troubleshooting only if necessary.
For recurring issues across business devices, Prismberry can help organizations assess network connectivity, DNS configuration, infrastructure monitoring, and network security to identify underlying problems.
Was this article helpful?
Thanks — noted.
Have a question we haven't covered?
Our specialists answer directly — no forms to chase, no sales script.
Ask a specialist









