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 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.
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.
Cloudflare has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes. The most common one overall is: The A or CNAME record for the hostname does not exist.
Add the missing record at the DNS provider. Remember that the apex and www are separate records.
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'.
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.
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.
The DNS lookup completed and the authoritative answer was 'this name does not exist'. Either the record is genuinely missing, the domain lapsed, or a recent DNS change has not propagated to the resolver you are using.