I kept getting “DNS_PROBE_FINISHED_NXDOMAIN” — here’s what actually fixed it

WebsiteDesignPro — Sat, 04 Apr 2026 17:41:07 +0000

I ran into this error recently while working on a site hosted on a VPS:

DNS_PROBE_FINISHED_NXDOMAIN

At first, I thought the server was down.

It wasn’t.

What I checked first (and got wrong)

My initial reaction was to check:

Nginx status
Server uptime
Firewall

Everything looked fine.

That’s when I realized — this isn’t really a “server” problem.

The actual issue

The problem was DNS.

The domain wasn’t properly resolving to the server IP.

In my case:

The A record was either missing or not updated correctly
And my system had cached the old DNS
What actually fixed it

Here’s exactly what I did:

Checked the A record
Made sure the domain points to the correct VPS IP

Ran:

ipconfig /flushdns

(on Windows)

Tested with:

nslookup mydomain.com

After that, it started resolving correctly.

One thing that confused me

Even after fixing DNS, the site didn’t load immediately.

That’s because of DNS propagation.

Sometimes it takes time — anywhere from a few minutes to several hours.

What I learned

This error looks scary, but most of the time:

It’s not your server
It’s not your code
It’s just DNS

If you’re facing this

Before restarting everything or blaming your hosting:

Check your DNS records
Test with nslookup
Clear your local cache

You’ll probably fix it faster than expected.

Final thought

Working with VPS has taught me one thing:

Small misconfigurations (like DNS) can look like big failures.

But once you understand the basics, debugging becomes much easier.

DEV Community: WebsiteDesignPro