DNS_PROBE_FINISHED_NXDOMAIN on Windows
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.
Is DNS_PROBE_FINISHED_NXDOMAIN happening on your 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'.
Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.
If that didn't fix it
Windows has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes that apply everywhere. The most common one overall is: the a or cname record for the hostname does not exist.
All causes and fixes for DNS_PROBE_FINISHED_NXDOMAIN