ERR_NAME_NOT_RESOLVED on Mac: 8 quick fixes (2026)

"This site can't be reached", "ERR_NAME_NOT_RESOLVED", "DNS_PROBE_FINISHED_NXDOMAIN"... These error messages are frustrating, especially when the Internet works for other sites. This guide will help you resolve these DNS issues on Mac.

Understanding the error

What's happening?

When you type "google.com" in your browser: 1. Your Mac asks for google.com's IP address 2. DNS servers respond with the IP (e.g., 142.250.185.78) 3. Your browser connects to that IP

ERR_NAME_NOT_RESOLVED means step 2 failed.

Possible causes

• Corrupted or stale DNS cache
• Unreachable or slow DNS servers
• Misconfigured hosts file
• Problematic VPN or proxy
• Firewall blocking DNS requests
• The site is actually down
• Internet connection problem

Solution #1: Flush DNS cache

This is the quickest solution and resolves 50% of cases.

sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder

Test immediately by reloading the page.

Solution #2: Check the hosts file

A domain blocked in your hosts file will cause this error.

cat /etc/hosts | grep "problem-domain.com"

If the domain appears with 0.0.0.0 or 127.0.0.1, it's blocked.

Unblock the domain

sudo nano /etc/hosts

Delete or comment out (#) the concerned line, then flush DNS cache.

Solution #3: Change DNS servers

Your ISP's DNS may be slow or failing.

Recommended DNS

Cloudflare (fast, private)

• 1.1.1.1
• 1.0.0.1

Google (reliable)

• 8.8.8.8
• 8.8.4.4

Quad9 (secure)

• 9.9.9.9
• 149.112.112.112

Change DNS on Mac

1. System Settings > Network 2. Select your connection (Wi-Fi or Ethernet) 3. Details... > DNS 4. Remove existing servers, add new ones 5. Click OK

Via Terminal

# Show current DNS
scutil --dns | grep "nameserver"

# Configure Cloudflare DNS (Wi-Fi)
networksetup -setdnsservers Wi-Fi 1.1.1.1 1.0.0.1

Solution #4: Disable VPN/Proxy

VPNs change your DNS servers and can cause problems.

Quick test

1. Disconnect your VPN 2. Flush DNS cache 3. Test the site

If it works, the problem is the VPN. Contact their support or switch VPN servers.

Check proxies

System Settings > Network > Wi-Fi > Details... > Proxies

Disable any configured proxy to test.

Solution #5: Restart network services

Disable/re-enable Wi-Fi

Click Wi-Fi icon > Turn Wi-Fi Off > Wait 10 seconds > Turn back on

Via Terminal

# Restart mDNSResponder
sudo killall -HUP mDNSResponder

# Restart network interface
sudo ifconfig en0 down && sudo ifconfig en0 up

Solution #6: Check the firewall

Mac firewall or security applications can block DNS requests.

Check macOS firewall

System Settings > Network > Firewall

Temporarily disable to test.

Third-party applications

Little Snitch, Lulu, or antiviruses can block DNS. Check their rules.

Solution #7: Renew IP address

# Release current IP
sudo ipconfig set en0 DHCP

# Or force renewal
sudo ipconfig set en0 BOOTP && sudo ipconfig set en0 DHCP

Solution #8: Check if the site is down

Maybe the problem isn't on your end.

Verification tools

• downforeveryoneorjustme.com
• isitdown.site

Test from another device

Try accessing the site from your phone on cellular (not Wi-Fi).

Advanced diagnosis

Check DNS resolution

# With nslookup
nslookup google.com

# With dig
dig google.com

# With host
host google.com

Expected result: an IP address.

Test with a specific DNS

# Test with Cloudflare DNS
nslookup google.com 1.1.1.1

# Test with Google DNS
nslookup google.com 8.8.8.8

If it works with an external DNS but not yours, change your DNS.

Check Internet connection

# Ping Google DNS
ping -c 4 8.8.8.8

# Ping by name (tests DNS)
ping -c 4 google.com

If ping by IP works but not by name, it's a DNS problem.

Similar errors

| Message | Meaning | |---------|---------| | ERR_NAME_NOT_RESOLVED | DNS resolution failed | | DNS_PROBE_FINISHED_NXDOMAIN | Non-existent domain | | ERR_CONNECTION_REFUSED | Server found but refuses connection | | ERR_CONNECTION_TIMED_OUT | Server not responding |

Prevention

Use reliable DNS

Configure Cloudflare (1.1.1.1) or Google (8.8.8.8) as primary DNS.

Avoid bulky hosts files

Too many entries can slow resolution. Use a tool like Locahl to manage cleanly.

Restart regularly

An occasional restart clears caches and resolves latent issues.

Conclusion

The ERR_NAME_NOT_RESOLVED error is almost always related to DNS cache or configured DNS servers. In 90% of cases, flushing DNS cache or changing DNS servers solves the problem.

If the problem persists on only one site, the site itself is probably the cause.