TroubleByteSearch
SOURCE VERIFIEDSource review Sep 6, 2026No hands-on test claimed2 sources

DNS_PROBE_FINISHED_NXDOMAIN: what it means and what to check

DNS_PROBE_FINISHED_NXDOMAIN means the DNS lookup completed with NXDOMAIN: the resolver determined that the requested name does not exist. For site owners, missing or incorrect DNS records are a primary place to check.

AuthorshipWritten and source-reviewed by Mihailo Ivanjac
Record created Sep 6, 2026Last source review Sep 6, 2026Source review only
SymptomA Chromium-family browser reports DNS_PROBE_FINISHED_NXDOMAIN, or another client reports that the hostname does not exist.
Problem familyNetworking · DNS
Highest step riskSafe
Editorial statePublic launch · indexed
Affected scope
Chrome and Chromium-family browsers (exact error string)Other browsers showing an equivalent DNS name-resolution failureCloudflare DNSDomain apex and subdomains
Start here

Verify the exact apex or subdomain DNS record

NXDOMAIN means DNS says the requested hostname does not exist. If you own the site, verify that the exact apex or subdomain has a DNS record and that it points to the intended target. If you are only a visitor, test another network or resolver because local DNS problems can produce similar symptoms.

  1. Identify the exact hostname that returns NXDOMAIN.
  2. Open the authoritative DNS zone for the domain.
  3. Confirm that the apex or subdomain has the expected A, AAAA, CNAME or provider-specific record.
  4. Correct the missing or wrong record and retest after DNS caches update.

Why this branch first: Cloudflare defines NXDOMAIN as a resolver result that the name does not exist and recommends checking expected apex and subdomain DNS records.

TroubleByte diagnostic diagram showing browser, resolver and authoritative DNS checks for NXDOMAIN.
DNS resolution path for NXDOMAINTroubleByte · Original TroubleByte editorial diagram
TroubleByte Tool

Inspect this hostname in public DNS

Check A, AAAA, CNAME, MX, NS and TXT records before changing DNS again.

Open DNS Inspector →
Visual diagnosis

TroubleByte diagnostic path

01
Hostname

Confirm the exact failing apex or subdomain.

02
Authoritative DNS

Check whether that exact name has a valid record.

03
Target

Verify the record points to the intended origin or tunnel.

04
Delegation

If NXDOMAIN persists, verify nameservers and zone status.

Original TroubleByte diagnostic map. It summarizes the cited troubleshooting order; it is not a vendor screenshot.

Decision checks

Use the symptom to choose the next branch

Do public or authoritative DNS lookups also return NXDOMAIN for the exact hostname?

YES

Treat this as authoritative DNS/delegation work: verify the exact record, zone and nameservers.

NO

Stop editing authoritative DNS; the problem is more likely local resolver, cache, device or network specific.

Is the failing name a subdomain such as www rather than the apex?

YES

Verify that exact subdomain has its own intended record or alias. Do not assume the apex record covers it.

NO

Verify the apex record and domain delegation before changing the web server.

Original TroubleByte decision aid derived from the cited troubleshooting scope. It does not replace vendor documentation.

Diagnosis

What this usually means

The exact DNS_PROBE_FINISHED_NXDOMAIN string is associated with Chromium-family browser diagnostics. Other browsers can report the same underlying DNS failure with different wording. The key question is whether the hostname is actually absent from public DNS or only failing for one client or network; a site-owner fix is different from visitor-side resolver troubleshooting.

What the evidence establishes

What we verified from the source material

Cloudflare defines NXDOMAIN as a DNS result indicating that the requested name does not exist and recommends checking the exact apex or subdomain record and its target. Cloudflare also notes that visitors can see similar browser symptoms because of local network or resolver issues, so this page separates site-owner DNS checks from visitor-side troubleshooting. Cloudflare’s DNS-record documentation also confirms the record types and TTL behavior used when correcting a missing or incorrect hostname record.

Before you change anything

Prerequisites and checks

Prepare first

  • Write down the exact failing hostname, including whether it contains www or another subdomain.
  • If you own the domain, identify the authoritative DNS provider before editing records.
  • Do not change the origin web server until public DNS resolution has been checked.

Checks that prevent the wrong fix

  • Check the exact hostname in the error; www.example.com and example.com are different DNS names.
  • If you just changed DNS, allow for propagation and resolver cache timing.
  • Do not change origin web-server settings until you confirm DNS resolves to the intended target.
Scope

Applies to

✓ Chrome and Chromium-family browsers (exact error string)✓ Other browsers showing an equivalent DNS name-resolution failure✓ Cloudflare DNS✓ Domain apex and subdomains
Troubleshooting path

Solutions, in order

01
SAFE · START HERE

Verify the exact apex or subdomain DNS record

  1. Identify the exact hostname that returns NXDOMAIN.
  2. Open the authoritative DNS zone for the domain.
  3. Confirm that the apex or subdomain has the expected A, AAAA, CNAME or provider-specific record.
  4. Correct the missing or wrong record and retest after DNS caches update.

Why this can work: Cloudflare defines NXDOMAIN as a resolver result that the name does not exist and recommends checking expected apex and subdomain DNS records.

02
SAFE

Confirm the DNS record points to the intended target

  1. Review the value of the DNS record that exists.
  2. Confirm it points to the current origin IP, tunnel target or canonical hostname expected by your setup.
  3. Correct stale targets if necessary.
  4. Retest with an authoritative or public DNS lookup.

Why this can work: Cloudflare specifically recommends checking that existing DNS records point to the correct origin when the records are present.

Verification

How to know the fix actually worked

  1. Query the exact hostname from at least one public resolver and confirm it returns the intended record instead of NXDOMAIN.
  2. Test both the apex and the affected subdomain when both are supposed to exist.
  3. After a DNS change, retest after the configured TTL/cache window rather than making multiple rapid edits.

Do not count a temporary disappearance of the symptom as a confirmed fix if the problem normally returns after a restart, reconnect or several minutes of use.

Stop conditions

When not to keep changing things

  • If authoritative nameservers themselves return NXDOMAIN for a record that exists in the dashboard, verify domain delegation and zone status with the DNS provider or registrar.
  • If only one device or network fails while public resolvers return the correct answer, stop editing authoritative DNS and troubleshoot the local resolver/network instead.

Escalation: If the correct DNS record exists but authoritative lookups still return NXDOMAIN, verify the domain’s delegated nameservers and zone status with the DNS provider or registrar.

Evidence

Sources used for this record

Primary · checked Sep 6, 2026Cloudflare — Fix DNS_PROBE_FINISHED_NXDOMAINOfficial documentation used to verify the troubleshooting steps.Corroborating · checked Sep 6, 2026Cloudflare — Manage DNS recordsOfficial Cloudflare documentation for creating and correcting A, AAAA and CNAME records and understanding TTL behavior.
Who reviewed this

Mihailo Ivanjac

This record was written and source-reviewed by Mihailo Ivanjac. Source review means the cited documentation was checked against the troubleshooting order on this page; it does not imply a hands-on reproduction unless the page explicitly says so.

Author profile and editorial scope →
Community troubleshooting

Discuss this exact problem

Share what happened on your system, ask a focused follow-up question, or add evidence that may help someone with the same symptom. Community posts are separate from TroubleByte editorial verification.

Before posting Do not include passwords, API keys, recovery codes, private IP addresses or other secrets. TroubleByte automatically attaches only coarse OS, browser and device-class context. Your full Browser & System Info report is not uploaded automatically.
Start a discussion
Posts are public. Guest identity is pseudonymous and browser-specific.

Loading community discussions…
Keep diagnosing

Related Networking problems

CloudflareCloudflare Error 523: Origin is unreachableCloudflare 523 is a routing/reachability problem: Cloudflare cannot contact the configured origin because the origin IP is wrong or the network path has no usable route. It is distinct from 521 refusal and 522 timeout, so the fastest checks are DNS origin address and routing evidence rather than application code.CloudflareCloudflare Error 524: A timeout occurredCloudflare 524 means the TCP connection to the origin succeeded, but the origin did not return an HTTP response within the proxy read timeout (125 seconds by default) or did not complete a write in time. That makes slow application work, long database queries and resource saturation more relevant than firewall reachability.CloudflareCloudflare Error 521: Web server is downCloudflare defines Error 521 as the origin web server refusing connections from Cloudflare. Common causes include an offline origin application or security rules blocking Cloudflare IP ranges.
Change log

Revision history

Show 7 recorded revisions

2026-09-06 — v0.6 media/performance pass: added a dedicated social preview card and an original diagnostic diagram; indexing remains disabled.

2026-09-06 — v0.5 UX/discovery pass: added decision-oriented diagnostic guidance and kept indexing disabled.

2026-09-06 — v0.4 depth pass: added symptom framing, prerequisites, verification checks and explicit stop conditions; indexing remains disabled.

2026-09-06 — v0.3 trust pass: assigned a named human author/source reviewer, added section taxonomy and an original diagnostic flow; indexing remains disabled.

2026-09-06 — Narrowed the exact browser-error scope to Chromium-family browsers and clarified that other browsers may show equivalent DNS failures with different wording.

2026-09-06 — Clarified source-review semantics and evidence scope; no hands-on hardware test is claimed.

2026-09-06 — Created from current Cloudflare DNS troubleshooting documentation; held noindex for review.