Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name.
Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name.
Settings → Network & internet → Private DNS → set to Automatic, then toggle airplane mode to clear the cache. Test the same domain on Wi-Fi and mobile data to isolate the resolver.
Android has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes. The most common one overall is: The A or CNAME record for the hostname does not exist.
Add the missing record at the DNS provider. Remember that the apex and www are separate records.
The DNS lookup queries public resolvers directly and shows the A, AAAA, CNAME and NS records that actually exist — which instantly separates 'record missing' from 'my resolver is stale'.
Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name.
Settings → Network & internet → Private DNS → set to Automatic, then toggle airplane mode to clear the cache. Test the same domain on Wi-Fi and mobile data to isolate the resolver.
The DNS lookup completed and the authoritative answer was 'this name does not exist'. Either the record is genuinely missing, the domain lapsed, or a recent DNS change has not propagated to the resolver you are using.