Platform-specific

    DNS_PROBE_FINISHED_NXDOMAIN on Cloudflare

    Why it happens on Cloudflare

    The record exists in the Cloudflare dashboard but the domain's nameservers at the registrar still point somewhere else, so Cloudflare's zone is never consulted.

    The fix on Cloudflare

    In the Cloudflare Overview tab, confirm the status is Active and the two assigned nameservers exactly match what the registrar has. A zone stuck in Pending Nameserver Update serves nothing.

    Is DNS_PROBE_FINISHED_NXDOMAIN happening on your domain?

    The DNS lookup queries public resolvers directly and shows the A, AAAA, CNAME and NS records that actually exist — which instantly separates 'record missing' from 'my resolver is stale'.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    If that didn't fix it

    Cloudflare has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes that apply everywhere. The most common one overall is: the a or cname record for the hostname does not exist.

    All causes and fixes for DNS_PROBE_FINISHED_NXDOMAIN

    DNS_PROBE_FINISHED_NXDOMAIN on other platforms and devices

    Monitor this continuously with LemWatch

    A one-off dns_probe_finished_nxdomain monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.