Android's Private DNS setting forces every lookup through a specified DoT provider; if that hostname is wrong or the provider is blocked on the current network, all resolution fails.
Android's Private DNS setting forces every lookup through a specified DoT provider; if that hostname is wrong or the provider is blocked on the current network, all resolution fails.
Settings → Network & internet → Private DNS → set to Automatic (or Off), then retry. Also test on mobile data to rule out a filtering Wi-Fi network.
Android 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.
Android's Private DNS setting forces every lookup through a specified DoT provider; if that hostname is wrong or the provider is blocked on the current network, all resolution fails.
Settings → Network & internet → Private DNS → set to Automatic (or Off), then retry. Also test on mobile data to rule out a filtering Wi-Fi network.
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.