The DNS_PROBE_FINISHED_NXDOMAIN error indicates that the DNS lookup failed because the domain name could not be resolved to an IP address. This typically happens when the DNS configuration for your domain is incorrect or incomplete. It is a common issue on hosting platforms, and here is how you can troubleshoot and resolve it.

What Does the Error Mean?

  1. DNS Lookup Failed: The browser was unable to find a valid IP address for the domain.
  2. NXDOMAIN: Stands for "Non-Existent Domain," meaning the DNS server could not find the domain.

Common Causes

Incorrect DNS Settings

DNS records (e.g., A, CNAME) are not configured or point to the wrong IP address.

Domain Not Pointed to Hosting

Nameservers for the domain are not updated to use the hosting provider DNS.

Propagation Delay

Changes to DNS records can take up to 48 hours to propagate globally.

Expired or Unregistered Domain

The domain may have expired or was never registered.

Local DNS Cache Issues

Your computer or browser may have cached old or incorrect DNS information.

Firewall or Network Issues

Firewalls or DNS settings on your network may block the lookup.

Registrar Lock or Suspensions

The domain might be locked or suspended at the registrar level.

How to Fix the Error

Verify DNS Records

  • Log in to your DNS hosting provider control panel and check the DNS records for the domain.
  • A Record: Points to the server IP address.
example.com IN A 192.168.1.1
  • CNAME Record: For subdomains pointing to another domain.
www.example.com IN CNAME example.com
  • NS Records: Ensure they match your hosting provider nameservers.
ns1.hostingprovider.com
ns2.hostingprovider.com

Update Nameservers

  • At your domain registrar, update the nameservers to point to your hosting provider.
  • Example: Go to the domain registrar (e.g., Namecheap, GoDaddy). Set nameservers:
ns1.yourhosting.com
ns2.yourhosting.com

Check Domain Status

Flush Local DNS Cache

Clear cached DNS entries on your computer to ensure you are using updated DNS information.

On Windows:

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

On macOS:

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

On Linux:

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

Use Public DNS Servers

Change your DNS settings to 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.

Wait for DNS Propagation

Restart Router and Device

  • Restart your router and device to ensure they are using updated network settings.

Check Hosting Configuration

  • Log in to your hosting provider control panel and verify:
  • The domain is correctly added to your account.
  • The server is configured to serve your domain.
  • Example: In cPanel, ensure the domain is added under Domains or Addon Domains.

Troubleshoot Local Network

  • If the issue persists on your network but works elsewhere:
  • Test using a mobile data connection or another network.
  • Check firewall or VPN configurations.

Example Scenario and Fix

Scenario: You recently moved your website to a new hosting provider, updated the nameservers, but see the error.

Fix:

  1. Verify nameservers at the registrar.
  2. Check DNS records on the hosting provider.
  3. Wait for DNS propagation and flush local DNS cache.

Helpful Tools for Troubleshooting

  1. Ping Command: Check if the domain resolves to an IP:
    2. ping example.com
  2. nslookup: Check DNS resolution:
    3. nslookup example.com
  3. Online DNS Tools:
  4. Traceroute: Check the route taken to resolve the domain:
    5. tracert example.com

The DNS_PROBE_FINISHED_NXDOMAIN error is typically caused by incorrect DNS settings or a delay in DNS propagation. By verifying DNS records, updating nameservers, flushing DNS caches, and ensuring proper domain configuration, you can resolve the issue. If problems persist, contact your hosting provider or domain registrar for assistance.