The DNS_PROBE_FINISHED_NXDOMAIN error occurs when a DNS (Domain Name System) lookup fails because the domain cannot be resolved to an IP address. This means your browser cannot find the server hosting the domain.

What Causes DNS Lookup Failure?

Incorrect DNS Records

The domain DNS records (e.g., A, CNAME) are missing or incorrectly configured.

Unregistered or Expired Domain

The domain name is not registered, or its registration has expired.

Incorrect Nameserver Configuration

The domain is not pointing to the correct DNS hosting provider via NS records.

Local DNS Cache Issues

Outdated or incorrect DNS information is cached on your computer or router.

Propagation Delay

Recent changes to DNS settings have not propagated globally.

Network or ISP Issues

Your internet service provider (ISP) or local network is unable to resolve the domain.

Firewall, VPN, or Proxy Blocking

A firewall, proxy, or VPN might block the DNS query.

DNS Service Down

The DNS server hosting the domain records is offline or misconfigured.

How to Fix DNS_PROBE_FINISHED_NXDOMAIN

Verify Domain Registration

  • Use a WHOIS Lookup Tool to check if the domain is registered and active:
  • WHOIS Lookup

Check DNS Records

  • Log in to your DNS hosting provider and verify that DNS records are correctly configured:
  • A Record: Maps the domain to the server IP address.
example.com IN A 192.168.1.1
  • CNAME Record: Alias subdomains to the main domain.
www.example.com IN CNAME example.com

Update Nameservers

  • Ensure the domain is pointing to the correct nameservers provided by your hosting provider.

Steps:

  1. Log in to your domain registrar (e.g., GoDaddy, Namecheap).
  2. Update the nameservers (NS records):
ns1.hostingprovider.com
ns2.hostingprovider.com
  1. Wait for DNS propagation (up to 48 hours).

Clear DNS Cache

Clearing DNS cache ensures your computer uses updated DNS records.

Windows:

  1. Open Command Prompt as Administrator.
  2. Run:
    3. ipconfig /flushdns

macOS:

  1. Open Terminal.
  2. Run:
    3. sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux:

  1. Open Terminal.
  2. Restart the DNS service:
    3. sudo systemctl restart systemd-resolved

Change DNS Server

  • Use reliable public DNS servers like Google DNS or Cloudflare DNS.

Google DNS:

  • Primary: 8.8.8.8
  • Secondary: 8.8.4.4

Cloudflare DNS:

  • Primary: 1.1.1.1
  • Secondary: 1.0.0.1

Steps to Change DNS (Windows):

  1. Go to Control Panel > Network and Sharing Center > Change Adapter Settings.
  2. Right-click your active connection and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Enter the DNS server addresses above.

Restart Your Router

  • Restart your router to refresh the network settings and resolve DNS issues.

Test on a Different Network

  • Try accessing the domain on another network (e.g., mobile data) to rule out local network issues.

Disable VPN, Proxy, or Firewall

  • Temporarily disable your VPN, proxy, or firewall to see if they are blocking DNS resolution.

Advanced Troubleshooting

Use nslookup

Run the nslookup command to test DNS resolution.

Example:

nslookup example.com

Output (Successful):

Server: dns.google
Address: 8.8.8.8

Name: example.com
Address: 192.168.1.1

Output (Failure):

** server can't find example.com: NXDOMAIN

Use tracert

Check the route to the domain.

Example:

tracert example.com

Check DNS Propagation

  • Use DNS Checker to verify if your domain DNS records are propagating globally.

Contact Your Hosting Provider

  • If the issue persists, contact your hosting provider or DNS hosting provider to ensure their DNS servers are functioning correctly.

The DNS_PROBE_FINISHED_NXDOMAIN error is usually caused by DNS misconfigurations, local cache issues, or domain status problems. By following the steps above, you can identify and resolve the issue to ensure your domain resolves correctly.