---
title: "DNS_PROBE_FINISHED_NXDOMAIN on Android: cause and fix"
description: "Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name."
canonical: "https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-android"
source: "https://lemwatch.com"
---

# DNS_PROBE_FINISHED_NXDOMAIN on Android

> Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name.

## Why it happens on Android

 Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name.

## The fix on Android

 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.

## If that didn't fix it

 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.

## Check your own domain

 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'.

## Frequently asked questions

### Why does DNS_PROBE_FINISHED_NXDOMAIN happen on Android?

 Android caches negative DNS answers aggressively and Private DNS (DNS over TLS) silently fails when the configured provider cannot resolve the name.

### How do I fix DNS_PROBE_FINISHED_NXDOMAIN on Android?

 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.

### What does DNS_PROBE_FINISHED_NXDOMAIN mean?

 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.


## Related

- [All causes of DNS_PROBE_FINISHED_NXDOMAIN](https://lemwatch.com/errors/dns-probe-finished-nxdomain)
- [All website error codes](https://lemwatch.com/errors)
- [DNS_PROBE_FINISHED_NXDOMAIN on iPhone](https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-iphone)
- [DNS_PROBE_FINISHED_NXDOMAIN on Windows](https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-windows)
- [DNS_PROBE_FINISHED_NXDOMAIN on Chrome](https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-chrome)
- [Free DNS lookup](https://lemwatch.com/tools/dns-lookup)
- [DNS_PROBE_FINISHED_NXDOMAIN on Shopify](https://lemwatch.com/errors/dns-probe-finished-nxdomain/in-shopify)
- [Website monitoring overview](https://lemwatch.com/website-monitoring)