A domain moved to Cloudflare resolves nowhere until the registrar's nameservers are changed — the DNS records exist in the dashboard but nothing on the internet is asked for them.
A domain moved to Cloudflare resolves nowhere until the registrar's nameservers are changed — the DNS records exist in the dashboard but nothing on the internet is asked for them.
In Cloudflare → DNS, confirm the assigned nameservers, then set exactly those two at the registrar. The lookup below shows which nameservers are authoritative right now.
Cloudflare has its own failure mode, but ERR_NAME_NOT_RESOLVED has a wider set of causes. The most common one overall is: No DNS record exists for the hostname.
Add the A or CNAME record. Check apex and www separately.
Resolving the name from outside your machine proves in one step whether the record exists at all or whether only your resolver is failing.
A domain moved to Cloudflare resolves nowhere until the registrar's nameservers are changed — the DNS records exist in the dashboard but nothing on the internet is asked for them.
In Cloudflare → DNS, confirm the assigned nameservers, then set exactly those two at the registrar. The lookup below shows which nameservers are authoritative right now.
Chrome could not turn the hostname into an IP address. Closely related to NXDOMAIN but broader: it also covers resolver failures and timeouts, not just definitive 'does not exist' answers.