Fix: DNS_PROBE_FINISHED_NO_INTERNET

DNS_PROBE_FINISHED_NO_INTERNET is a Google Chrome error that appears when your browser can't resolve domain names to IP addresses. Despite the name, it doesn't always mean your internet connection is completely down — it often indicates a DNS-specific problem that's easy to fix. Understanding how DNS works is the first step to resolving this error quickly.

What This Error Means

When you see this error, Chrome attempted a DNS lookup and failed. The browser couldn't translate the domain name (like example.com) into an IP address, so it can't load the page. This is fundamentally a name resolution failure: your device can't reach the DNS resolver it's configured to use, or the resolver itself can't find an answer.

Common causes:

• Your DNS server is unreachable or misconfigured
• Your local DNS cache contains stale or corrupted entries
• A firewall or antivirus is blocking DNS traffic
• Your network adapter's DNS settings are wrong
• Your internet connection is actually down
• DNS over HTTPS (DoH) settings in Chrome are conflicting with your network
• Your ISP's DNS servers are experiencing an outage

Diagnosing the Problem

Before jumping into fixes, it helps to narrow down the cause. Open a terminal or command prompt and run a few diagnostic commands.

Test Basic Connectivity

# Can you reach the internet at all?
ping 8.8.8.8
 
# Can you reach your default gateway?
# (Windows)
ipconfig | findstr "Default Gateway"
# macOS
route -n get default
# Linux
ip route show default

A successful ping confirms reachability to that IP, not that DNS or HTTPS works. A failed ping can mean packet filtering rather than a lost connection. Compare the DNS tests below and test another device before changing settings.

Test DNS Resolution Directly

# Try resolving a domain using your system resolver
nslookup example.com
 
# Try resolving against a public DNS server directly
nslookup example.com 8.8.8.8
 
# Using dig for more detailed output
dig example.com @8.8.8.8

If nslookup example.com 8.8.8.8 works but nslookup example.com does not, the problem is with your configured DNS server, not your internet connection. This tells you exactly which fix to apply: change your DNS server.

Check Which DNS Server You're Using

# macOS: shows per-interface and VPN resolver settings
scutil --dns
 
# Linux with systemd-resolved
resolvectl status
# Other Linux resolver configurations
cat /etc/resolv.conf
 
# Windows
ipconfig /all | findstr "DNS"

If the DNS server listed is your router's IP (like 192.168.1.1), your router may be failing to forward DNS queries. Try bypassing it by pointing directly to a public resolver.

Quick Fixes (Try These First)

1. Check Your Internet Connection

Before troubleshooting DNS, verify basic connectivity:

• Can you access your router's admin page (usually 192.168.1.1)?
• Can you ping an IP address directly?

ping 8.8.8.8

Use ping as one signal. If a known website works despite a failed ping, ICMP may be filtered. If multiple devices cannot reach websites or resolve names, check the router, captive portal, and internet connection.

2. Restart Your Browser

Close Chrome completely and reopen it. Chrome maintains its own DNS cache that can become stale. On macOS, make sure to fully quit Chrome (Cmd+Q), as closing the window doesn't terminate the process.

3. Try Incognito Mode

Open an incognito window (Ctrl+Shift+N or Cmd+Shift+N) and try loading the page. If it works, a Chrome extension may be interfering with DNS. Extensions like ad blockers, VPN extensions, or privacy tools sometimes intercept DNS queries.

4. Try a Different Browser

Open Firefox or Safari and try loading the same page. If other browsers work, the problem is specific to Chrome's DNS handling. If all browsers fail, the problem is at the OS or network level.

Solution 1: Flush Your DNS Cache

A stale local DNS cache is one possible cause. A cached NXDOMAIN response or an outdated A record address can prevent resolution even after the actual DNS records have been fixed. Clear the cache at both the OS and browser level.

Flush OS DNS Cache

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd-resolved):

sudo resolvectl flush-caches

Flush Chrome's DNS Cache

1. Open Chrome and navigate to chrome://net-internals/#dns
2. Click Clear host cache
3. Go to chrome://net-internals/#sockets and click Flush socket pools

For a complete guide, see How to Flush Your DNS Cache.

Solution 2: Change Your DNS Server

Your default DNS server (usually provided by your ISP) may be slow or down. Switch to a reliable public DNS. This is one of the most effective fixes because ISP DNS servers are a common point of failure.

Windows

1. Open Settings -> Network & Internet -> Change adapter options
2. Right-click your active connection -> Properties
3. Select Internet Protocol Version 4 (TCP/IPv4) -> Properties
4. Select Use the following DNS server addresses:
   • Preferred: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)
   • Alternate: 8.8.4.4 (Google) or 1.0.0.1 (Cloudflare)
5. Click OK and restart your browser

For IPv6 connectivity, also configure Internet Protocol Version 6 (TCP/IPv6):

• Preferred: 2001:4860:4860::8888
• Alternate: 2001:4860:4860::8844

macOS

1. Open System Settings -> Network
2. Select your active connection -> Details -> DNS
3. Remove existing entries and add:
   • 8.8.8.8
   • 8.8.4.4
4. Click OK

Linux

Use your distribution's NetworkManager connection settings or resolver configuration. /etc/resolv.conf is often generated automatically; directly editing it may be overwritten. The entries below illustrate the intended resolver addresses:

# /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

Or if using systemd-resolved, edit /etc/systemd/resolved.conf:

[Resolve]
DNS=8.8.8.8 8.8.4.4

Then restart the service:

sudo systemctl restart systemd-resolved

Verify the Change

After changing your DNS server, confirm it's working:

dig example.com
 
# You should see the response coming from your new server
# Check the "SERVER:" line in the output

Solution 3: Reset Network Settings

Windows

Open Command Prompt as Administrator and run:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your computer after running these commands.

macOS

Toggle Wi-Fi off and on, or disconnect and reconnect Ethernet. If that does not help, review the selected connection under System Settings → Network → Details, including DNS and proxies. Removing and recreating a network service is a last resort after recording its settings.

Linux

sudo systemctl restart NetworkManager

Solution 4: Disable VPN and Proxy

VPNs and proxy servers can interfere with DNS resolution:

1. Temporarily disconnect your VPN and try loading the page
2. Check proxy settings: Chrome -> Settings -> System -> Open your computer's proxy settings
3. Ensure Automatically detect settings is enabled and no manual proxy is configured

Some VPN clients install their own DNS resolver that intercepts all queries. When the VPN disconnects improperly, your system may still be pointed at a DNS server that's no longer reachable. Restarting your network adapter usually clears this state.

Solution 5: Check Chrome's DNS Over HTTPS Settings

Chrome has a built-in DNS over HTTPS (DoH) feature that can sometimes conflict with network configurations, especially on corporate or school networks:

1. Go to chrome://settings/security
2. Look for Use secure DNS
3. Try toggling this setting — if it's on, turn it off (or vice versa)
4. If you keep it on, try selecting a specific provider like Google or Cloudflare instead of "With your current service provider"

Solution 6: Check Firewall or Security Software

Some security software blocks DNS traffic (port 53):

1. Inspect recent block events or DNS-filter logs.
2. Compare the failing lookup with the network's intended resolver.
3. Correct a specific blocked rule with your administrator or security vendor. Keep protection enabled; a blanket firewall shutdown is not a useful first diagnostic.

Also check that port 853 (DNS over TLS) and port 443 (DNS over HTTPS) are not being blocked if you use encrypted DNS.

Solution 7: Reset Chrome Flags

Experimental Chrome features can cause DNS issues:

1. Navigate to chrome://flags
2. Click Reset all at the top
3. Restart Chrome

Flag names and availability change between Chrome versions. Prefer the supported Secure DNS setting above; reset flags only if you previously changed experimental settings.

If You're a DNS Administrator

If users are reporting this error when accessing domains you manage, the issue may be on the authoritative DNS side:

• Check your nameservers are responding: dig example.com @ns1.dnscale.eu
• Verify your records exist: NXDOMAIN means the queried name does not exist and is a different diagnosis from this connectivity probe result
• Check TTL values — if you recently deleted and recreated records, the old NXDOMAIN may be cached
• Review negative caching: a negative response uses the smaller of the SOA record's TTL and MINIMUM field
• Test from multiple locations — the issue may be related to DNS propagation delays
• Verify all NS records are responding correctly

# Check if your zone is resolving from the authoritative server
dig example.com @ns1.dnscale.eu +short
 
# Check if the zone has proper NS delegation
dig NS example.com
 
# Verify the SOA record for negative caching TTL
dig SOA example.com +short
 
# Request DNSSEC records (this command does not itself validate them)
dig example.com @1.1.1.1 +dnssec
# Compare with checking disabled when diagnosing validation failures
dig example.com @1.1.1.1 +dnssec +cd

A broken DNSSEC chain can cause SERVFAIL at a validating resolver. Do not infer the DNS response code from the browser error alone. If a normal query returns SERVFAIL but a checking-disabled query succeeds, investigate DNSSEC validation.

Conclusion

DNS_PROBE_FINISHED_NO_INTERNET is almost always fixable. Start by comparing connectivity and DNS results, then apply the fix for the failing layer. If those don't work, systematically check your VPN settings, firewall rules, and Chrome's DoH configuration. For DNS administrators, ensure your authoritative servers are healthy, records are correctly configured in DNScale, and DNSSEC signatures (if enabled) are valid. The key is to isolate whether the problem is local (your machine), network-level (your router or ISP), or server-side (the authoritative DNS).