---
title: "DNS_PROBE_FINISHED_NXDOMAIN on Windows: cause and fix"
description: "The Windows DNS Client service caches negative answers, so a fixed record can keep failing on that machine long after it works elsewhere."
canonical: "https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-windows"
source: "https://lemwatch.com"
---

# DNS_PROBE_FINISHED_NXDOMAIN on Windows

> The Windows DNS Client service caches negative answers, so a fixed record can keep failing on that machine long after it works elsewhere.

## Why it happens on Windows

 The Windows DNS Client service caches negative answers, so a fixed record can keep failing on that machine long after it works elsewhere.

## The fix on Windows

 Run `ipconfig /flushdns` in an elevated prompt, then `nslookup yourdomain.com 1.1.1.1` to bypass the local resolver and confirm the record now exists.

## If that didn't fix it

 Windows 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 Windows?

 The Windows DNS Client service caches negative answers, so a fixed record can keep failing on that machine long after it works elsewhere.

### How do I fix DNS_PROBE_FINISHED_NXDOMAIN on Windows?

 Run `ipconfig /flushdns` in an elevated prompt, then `nslookup yourdomain.com 1.1.1.1` to bypass the local resolver and confirm the record now exists.

### 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 Android](https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-android)
- [DNS_PROBE_FINISHED_NXDOMAIN on iPhone](https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-iphone)
- [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_STARTED: Chrome's DNS probe is still running](https://lemwatch.com/errors/dns-probe-started)
- [DNS_PROBE_FINISHED_NXDOMAIN on Mac](https://lemwatch.com/errors/dns-probe-finished-nxdomain/on-mac)