Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome.
Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome.
Open chrome://net-internals/#dns → Clear host cache, then chrome://net-internals/#sockets → Flush socket pools. If Secure DNS is on under Settings → Privacy → Security, switch it to 'With your current service provider' to test.
Chrome 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.
Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome.
Open chrome://net-internals/#dns → Clear host cache, then chrome://net-internals/#sockets → Flush socket pools. If Secure DNS is on under Settings → Privacy → Security, switch it to 'With your current service provider' to test.
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.