DNS Not Resolved Error

Fix 'DNS not resolved' or 'net::ERR_NAME_NOT_RESOLVED' errors. Learn how DNS resolution works and how to fix domain name lookup failures.

What Does This Error Mean?

The 'ERR_NAME_NOT_RESOLVED' error (or 'DNS_PROBE_FINISHED_NXDOMAIN') means the browser could not find the IP address for the domain name. DNS resolution failed because the domain does not exist, the DNS server cannot find it, or there is a network connectivity issue.

Common Causes

Domain name is misspelled or does not exist

DNS server is unavailable or not responding

DNS record (A, AAAA, CNAME) has not been created or propagated

Local DNS cache has stale or corrupted entries

Hosts file has an incorrect mapping for the domain

ISP or corporate DNS server is blocking the domain

How to Fix It

Flush DNS cache

Clear your local DNS cache to force fresh DNS resolution.

# Windows
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux
sudo systemctl restart systemd-resolved
# or
sudo resolvectl flush-caches

Check DNS records

Verify the domain has the correct DNS records configured.

# Check A record (IPv4)
nslookup example.com
# or
dig example.com A

# Check CNAME record
dig www.example.com CNAME

# Check nameservers
dig example.com NS

Try alternative DNS servers

Temporarily switch to a public DNS server like Cloudflare (1.1.1.1) or Google (8.8.8.8) to test.

# Windows: change DNS in network settings
# Or use command:
netsh interface ip set dns "Wi-Fi" static 1.1.1.1

# Test with specific DNS server
nslookup example.com 8.8.8.8
dig @1.1.1.1 example.com

Related Tools

Use these tools to debug and fix this error:

IP Lookup

Display your public IP address, browser information, and HTTP request details.

HTTP Status Code Reference

Searchable reference of all HTTP status codes with descriptions and use cases.

REST API Client

Send HTTP requests (GET, POST, PUT, DELETE) and inspect responses from your browser.

Related Errors

Other common errors in this category:

SSL Certificate Expired Error

Fix 'NET::ERR_CERT_DATE_INVALID' and 'SSL certificate expired' errors in browsers. Learn how to update and manage SSL/TLS certificates.

Connection Refused Error

Fix 'ECONNREFUSED' and 'Connection refused' errors when connecting to databases, APIs, or other services.

ERR_CONNECTION_RESET Error

Fix 'ERR_CONNECTION_RESET' or 'net::ERR_CONNECTION_RESET' errors in Chrome and other browsers. Learn why TCP connections are reset and how to fix them.

ERR_SSL_PROTOCOL_ERROR Error

Fix 'ERR_SSL_PROTOCOL_ERROR' errors in Chrome and browsers. Learn how SSL/TLS handshake failures happen and how to fix protocol mismatches.

Frequently Asked Questions

How long does DNS propagation take?

DNS changes typically propagate within a few minutes to 48 hours. TTL (Time To Live) values determine how long DNS resolvers cache the old records.

What is DNS_PROBE_FINISHED_NXDOMAIN?

This Chrome error means the DNS server responded that the domain does not exist. It's more specific than ERR_NAME_NOT_RESOLVED, which may also indicate connectivity issues.

Browse All Error Guides