Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix DNS_PROBE_FINISHED_NXDOMAIN in WordPress

Short answer

DNS_PROBE_FINISHED_NXDOMAIN means the DNS lookup finished and found no record for that domain name. First check the spelling, flush your local DNS cache, and test the site on another network. If the domain is yours, check its A record, www record, nameservers, and registration status, because a missing record or wrong nameserver is the usual cause.

Key takeaways

  • DNS_PROBE_FINISHED_NXDOMAIN means DNS found no record for the domain, not that the WordPress server crashed.
  • Google Public DNS uses 8.8.8.8 and 8.8.4.4, while Cloudflare 1.1.1.1 uses 1.1.1.1 and 1.0.0.1.
  • A missing A record for the apex domain or www subdomain is a common cause on a new WordPress site.
  • Cloudflare says to wait up to 24 hours after a nameserver change at the registrar.
  • A negatively cached NXDOMAIN answer can outlast a new DNS record, so waiting is sometimes the only fix.
  • If the domain fails on every network, the fault is with the domain, not with your browser.

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

DNS_PROBE_FINISHED_NXDOMAIN means the DNS lookup finished and the domain was found to have no DNS record.

DNS is the system that turns a domain name into an IP address. A WordPress site is a set of files and a database on a server, and the browser needs that IP address before it can ask the server for a page.

Cloudflare explains the code in plain terms: the DNS probe ran to completion, NXDOMAIN stands for non-existent domain, and the resolver found no associated DNS records. That is why the page never starts to load.

The error does not mean WordPress is broken. It means the browser never reached WordPress at all, so plugin and theme fixes will not help until DNS points to the right server.

How do you tell if the fault is on your device or on the domain?

Test the same domain on another network and with a public DNS lookup, because that split shows which side owns the fault.

Open the site on mobile data while your computer stays on Wi-Fi. If it loads on mobile data, the fault sits with your computer or your first network.

If it fails on both networks, ask a public resolver directly. Open https://dns.google/resolve?name=example.com&type=A in a browser and replace example.com with your domain. A result with an IP address means the domain exists in public DNS.

Google Public DNS also offers a cache purge and lookup page, and Cloudflare offers a purge for its 1.1.1.1 resolver, as noted in Cloudflare DNS troubleshooting. Use those pages only to test, not as a fix for a missing record.

What causes DNS_PROBE_FINISHED_NXDOMAIN most often?

A typo, a missing DNS record, wrong nameservers, a stale negative cache, or an expired domain cause most cases.

Work through the causes in this order, because the quick checks come first and the domain checks come last.

CauseWho sees itFirst check
Typo in the addressOne visitorRead the address letter by letter
Missing A or www recordEveryoneLook for the apex and www records
Wrong nameserversEveryoneCheck the nameservers at the registrar
Negative DNS cacheSome visitorsWait for the SOA MINIMUM time to pass
Expired or held domainEveryoneCheck expiry and status at the registrar

Cloudflare lists a mistyped domain, missing records, DNSSEC left on before a move to Cloudflare, and nameservers that no longer point to Cloudflare among the common causes in its general DNS issues guide.

A domain can also fail after a recent change. If someone looked up the name before the record existed, the resolver may have stored a negative answer, and that stored answer can keep the error alive after the record is added.

How do you fix it on your own computer first?

Check the address, restart Chrome, try an Incognito window, and pause VPN or filtering software one item at a time.

Google Chrome Help puts checking the website URL and reloading the page first, then checking the internet connection, in its connection error guide. A single wrong letter, such as .co instead of .com, returns exactly this error.

Next, open the address in an Incognito window. If it loads there, an extension or stored site data is involved, so disable extensions one by one and retest after each change.

Then pause your VPN, ad blocker, parental filter, or antivirus web shield one at a time. Each of these can change which DNS server answers you, so turn each one back on after the test.

Restart your router if every device on the same network fails. A router restart clears the router cache and asks for a fresh connection, and it takes only a few minutes.

How do you flush the DNS cache on Windows and macOS?

Flush the operating system cache and Chrome's own host cache, because Chrome keeps a separate cache from Windows and macOS.

On Windows, open Command Prompt as administrator and run ipconfig /flushdns, then press Enter. Microsoft says /flushdns flushes and resets the DNS client resolver cache and discards negative cache entries, as stated in its ipconfig reference.

On macOS, open Terminal and run sudo dscacheutil -flushcache, then run sudo killall -HUP mDNSResponder and press Enter. Enter your Mac password when asked, then restart the browser and reload the page.

For Chrome, open a new tab, go to chrome://net-internals/#dns, and click “Clear host cache”. Then open chrome://net-internals/#sockets and click “Flush socket pools” so old connections close.

A local flush only clears your own device. It does not clear your provider cache or fix a missing record on the domain, so move on if the error stays after a flush.

How do you switch to Google Public DNS or Cloudflare 1.1.1.1?

Change your DNS server to a public resolver to test whether your provider resolver is giving the wrong answer.

Write down your current DNS settings first, so you can restore them. Google gives the same advice before any change in its Public DNS setup guide.

ResolverIPv4 primaryIPv4 secondaryIPv6 primary
Google Public DNS8.8.8.88.8.4.42001:4860:4860::8888
Cloudflare 1.1.1.11.1.1.11.0.0.12606:4700:4700::1111

Google lists 8.8.8.8 and 8.8.4.4 as its IPv4 addresses, with 2001:4860:4860::8888 and 2001:4860:4860::8844 for IPv6, in the same Public DNS setup guide. Cloudflare lists 1.1.1.1 and 1.0.0.1 for IPv4, with 2606:4700:4700::1111 and 2606:4700:4700::1001 for IPv6, in its 1.1.1.1 Windows setup guide.

Switch DNS on Windows 11

  1. Open “Settings”, then “Network & internet”, then your connection.
  2. Open “DNS server assignment”, choose “Edit”, then choose “Manual”.
  3. Turn on IPv4, enter 8.8.8.8 and 8.8.4.4, or enter 1.1.1.1 and 1.0.0.1.
  4. Save, close the browser, reopen it, and reload the site.

Switch DNS on macOS

  1. Open “System Settings”, then “Network”, then your Wi-Fi or Ethernet connection.
  2. Open “Details”, then “DNS”, and click the plus sign to add a server.
  3. Add 8.8.8.8 and 8.8.4.4, or add 1.1.1.1 and 1.0.0.1, then click “OK”.
  4. Reload the site in a fresh browser window.

If the site loads after the switch, your first resolver was the fault. Keep the public resolver or ask your provider why its resolver fails for that name.

How do you fix it when the WordPress domain is yours?

Check the apex record, the www record, the origin IP, and the nameservers in that order.

Log in to your DNS provider, which may be Cloudflare, your host, or your registrar. Open the DNS records page and look for the zone apex, which is the bare domain such as example.com, plus www.

Cloudflare advises checking the apex domain and subdomains such as www.example.com and blog.example.com, then adding a missing apex or subdomain record, in its NXDOMAIN fix guide. If the record exists, check that it points to the correct origin IP from your host.

A common gap is a working apex with no www record, or the reverse. Add the missing record with the same IP or the same CNAME target as the working one, then save it.

If you use Cloudflare, check the proxy status too. Only A, AAAA, and CNAME records can be proxied, and a record set to DNS only still needs a correct IP. For related Cloudflare settings, see how to set up Cloudflare for WordPress.

Turn DNSSEC off at your registrar before you move a domain to Cloudflare. Cloudflare warns that DNS resolution fails if DNSSEC stays on during the move, in its general DNS issues guide.

How long should you wait for DNS changes to take effect?

Wait a few minutes for a record change, and up to 24 hours for a nameserver change.

Cloudflare says you may need to wait a few minutes after a DNS record change, in its NXDOMAIN fix guide. That short wait covers most record edits.

A nameserver change is slower. Cloudflare says to wait up to 24 hours while your registrar updates your nameservers, and to copy the two assigned nameserver names exactly, in its full setup guide. For the full timeline, see how long DNS propagation takes.

Negative caching can stretch the wait. RFC 2308 says a negative answer is cached with a TTL taken from the minimum of the SOA MINIMUM field and the SOA TTL, as stated in RFC 2308. Lowering the new record TTL will not clear an entry that already exists.

TTL also sets the normal cache time. Cloudflare says proxied records use an Auto TTL of 300 seconds, which is 5 minutes and cannot be edited, while DNS-only records can use 60 seconds to 1 day, in its TTL reference.

How do you check that the fix worked?

Reload the page in a fresh browser window, then test the domain with a public DNS lookup and from another network.

Start with a hard reload and a new Incognito window, so a stored page or a stored DNS answer does not hide the result. If the home page loads, open one post and the WordPress admin login page.

Next, run the public lookup again at https://dns.google/resolve?name=example.com&type=A with your domain in place of example.com. A result with your host IP means public DNS now has the record.

You can also query the authoritative nameserver directly with dig @1.1.1.1 example.com NS +short to list the nameservers, then query one of them for the A record. If the authoritative server returns the record, other resolvers should follow after their caches expire.

Check both the apex and www versions of the address. A fix that works for one and fails for the other means one record is still missing, so add it before you call the job done.

When should you contact your host or registrar?

Contact your host when the DNS records look right but the site still fails, and contact your registrar when the domain itself is expired, held, or pointing at the wrong nameservers.

Send your host the domain name, the A record value, the nameservers in use, and the exact time of the last failed load. Ask them to confirm the origin IP and to check whether the account or server is suspended.

Contact your registrar if the domain shows an expiry date in the past, a hold status such as clientHold, or nameservers you did not set. A hold stops the registry from publishing the domain in DNS, so no DNS edit can fix it until the registrar clears it.

If you moved hosts, ask the new host for the exact A record and nameserver values in writing. Then compare each value letter by letter with the values in your DNS panel.

One wrong digit in an IP address sends visitors nowhere. If the move involved a full site move, read how to move a WordPress site without losing SEO.

What mistakes should you avoid?

Do not edit the wrong zone, do not delete records you have not copied, and do not keep changing settings while propagation is still running.

Copy every DNS record before you change nameservers, because the new provider does not always import mail and subdomain records. A missing MX record after a move can stop email even when the website loads.

Do not lower the TTL after the change and expect instant results. The old TTL governs answers already cached, so plan the lower TTL a day before a move when you can.

Do not blame WordPress or reinstall it for a DNS error. WordPress cannot load until DNS resolves, and a reinstall will not add a missing A record or fix a wrong nameserver.

Check SSL only after DNS works. A certificate error is a separate fault from NXDOMAIN, and fixing it first wastes time while the domain still does not resolve. For the SSL step, see Cloudflare SSL settings for WordPress.

Frequently asked questions

Does DNS_PROBE_FINISHED_NXDOMAIN mean my WordPress site is hacked?

No. The error means DNS found no record for the domain, so the browser never reached WordPress. A hack would usually show a changed page, a redirect, or a warning after the site loads. Check the DNS records, nameservers, and domain expiry first, and look for hacking signs only after the site loads again.

How long does DNS_PROBE_FINISHED_NXDOMAIN last after I fix the DNS record?

Most record fixes show within a few minutes, but a nameserver change can take up to 24 hours. A negative cache can also delay the fix, because some resolvers keep the old does-not-exist answer until its timer ends. If the record is correct on the authoritative nameserver, wait and retest from another network.

Why does the site load on my phone but not on my computer?

Your phone and computer may use different networks and different DNS resolvers, and each one keeps its own cache. Flush the DNS cache on the computer, clear the browser host cache, and try a public DNS server such as 8.8.8.8 or 1.1.1.1. If the phone still loads and the computer does not, the fault is local to the computer or its network.

Can a VPN cause DNS_PROBE_FINISHED_NXDOMAIN?

Yes. A VPN can send DNS lookups through its own resolver, and that resolver may block or fail to resolve the domain. Pause the VPN, reload the page, and see if the site loads. If it does, check the VPN DNS settings or keep the VPN off while you visit that site, then turn it back on for other browsing.

What should I check first if the error appears right after I buy a new domain?

Check that the domain is registered and active, that nameservers point to your DNS provider, and that an A record exists for the apex domain and for the www version. New domains can also show this error while nameserver changes spread, so allow up to 24 hours. If the registrar shows a hold status, contact the registrar before changing DNS records.

Sources

  1. Fix DNS_PROBE_FINISHED_NXDOMAIN Cloudflare
  2. General DNS issues Cloudflare
  3. Change your nameservers (Full setup) Cloudflare
  4. Get Started with Google Public DNS Google for Developers
  5. Fix connection and loading errors in Chrome Google Chrome Help
  6. Set up 1.1.1.1 on Windows Cloudflare
  7. Ipconfig Microsoft Learn
  8. Negative Caching of DNS Queries (RFC 2308) IETF Datatracker

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test