Introducing PostScale -- email API for transactional, inbound, and masked addresses. PostScale

    Fix: DNS_PROBE_FINISHED_NO_INTERNET

    Learn what the DNS_PROBE_FINISHED_NO_INTERNET error means and how to fix it on Windows, macOS, Linux, and Chrome with step-by-step solutions.

    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.

    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.

    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

    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

    If the ping works but websites don't load, the problem is DNS-specific. If the ping fails, the issue is your network connection itself.

    2. Restart Your Browser

    Close Chrome completely and reopen it. Chrome maintains its own DNS cache that can become stale.

    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.

    Solution 1: Flush Your DNS Cache

    Stale DNS cache is the most common cause. Clear it 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:

    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

    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

    Edit /etc/resolv.conf or your NetworkManager settings:

    # /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

    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

    1. Open System Settings → Network
    2. Select your connection → click the minus (-) button to remove it
    3. Click the plus (+) button to re-add it
    4. Or simply toggle Wi-Fi off and on

    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

    Solution 5: Disable Firewall or Antivirus Temporarily

    Some security software blocks DNS traffic (port 53):

    1. Temporarily disable your firewall/antivirus
    2. Try loading the page
    3. If it works, add an exception for DNS traffic (UDP/TCP port 53) rather than leaving the firewall disabled

    Solution 6: 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

    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: an NXDOMAIN response (no records) triggers this error in Chrome
    • Check TTL values — if you recently deleted and recreated records, the old NXDOMAIN may be cached
    • Review your SOA record's minimum TTL — this controls negative caching duration (see What Is an SOA Record)

    Conclusion

    DNS_PROBE_FINISHED_NO_INTERNET is almost always fixable. Start with flushing your DNS cache and switching to a public DNS server — these two steps resolve the issue for most users. If you manage DNS zones, ensure your authoritative servers are healthy and records are correctly configured in DNScale.