A stale entry in the Windows hosts file or a leftover VPN DNS suffix overrides public DNS, so the name resolves to nothing.
A stale entry in the Windows hosts file or a leftover VPN DNS suffix overrides public DNS, so the name resolves to nothing.
Run ipconfig /flushdns in an elevated prompt, then inspect C:\\Windows\\System32\\drivers\\etc\\hosts for the domain and remove any stale line.
Windows 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 stale entry in the Windows hosts file or a leftover VPN DNS suffix overrides public DNS, so the name resolves to nothing.
Run ipconfig /flushdns in an elevated prompt, then inspect C:\\Windows\\System32\\drivers\\etc\\hosts for the domain and remove any stale line.
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.