ERR_NAME_NOT_RESOLVED on Chrome
Why it happens on 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.
The fix on 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.
Is ERR_NAME_NOT_RESOLVED happening on your domain?
Resolving the name from outside your machine shows whether public resolvers can find a record, helping distinguish a public DNS issue from a local resolver or network problem.
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
Chrome has its own failure mode, but ERR_NAME_NOT_RESOLVED has a wider set of causes that apply everywhere. The most common one overall is: no dns record exists for the hostname.
All causes and fixes for ERR_NAME_NOT_RESOLVED