My Website Shows “DNS_PROBE_STARTED” — What It Means & How to Fix It (2026)

Ellnotes24

My Website Shows “DNS_PROBE_STARTED” — What It Means & How to Fix It (2026)

Seeing DNS_PROBE_STARTED when you open your website can be confusing — especially if everything looks configured correctly.
This guide explains what the error means, why it happens, and exactly how to fix it, step by step.

—

✅ Quick Answer (For Google & Busy Readers)

DNS_PROBE_STARTED means your browser started checking DNS records but couldn’t complete the lookup.
This is usually caused by missing or incorrect DNS records, wrong nameservers, or DNS propagation delays.

👉 Fix it by verifying nameservers, A records, and DNS propagation.

—

❓ What Does “DNS_PROBE_STARTED” Actually Mean?

DNS (Domain Name System) translates your domain name (example.com) into a server IP address.

When you see DNS_PROBE_STARTED, it means:

The browser asked DNS for the site’s IP
DNS didn’t respond correctly or completely
The connection could not continue

This is not a website code error — it’s a DNS configuration issue.

—

🔍 Most Common Causes (90% of Cases)

Nameservers not set or set incorrectly
Missing or wrong A record
Domain newly registered (propagation delay)
DNS pointing to the wrong server IP
DNS cache issues (local or ISP)
Conflicting DNS providers (Cloudflare + hosting DNS)

—

🛠️ FIX 1: Check Your Nameservers (CRITICAL)

Go to your domain registrar (where you bought the domain).

Your nameservers should be exactly what your DNS provider gives you.

Example (Correct):

$$
ns1.exampledns.com
ns2.exampledns.com
$$

❌ Common mistake:

Mixing hosting DNS and Cloudflare DNS
Using old nameservers from a previous host

⚠️ Nameservers must match one provider only.

—

🛠️ FIX 2: Verify Your A Record

Your domain must point to your server IP.

Correct A record:

Type	Host	Value	TTL
A	@	YOUR_SERVER_IP	Auto / 300

Also add:

Type	Host	Value
A	www	YOUR_SERVER_IP

If this is missing or wrong → DNS_PROBE_STARTED appears.

—

🛠️ FIX 3: DNS Propagation (Be Patient)

DNS changes can take:

5 minutes
Up to 24–48 hours

During this time:

Some users see the site
Others see DNS_PROBE_STARTED

You can check propagation using:

DNS Checker tools
nslookup yourdomain.com
dig yourdomain.com

—

🛠️ FIX 4: Cloudflare Users (Very Common)

If you use Cloudflare:

Checklist:

Nameservers point to Cloudflare ✔
A record exists ✔
Proxy (orange cloud) can be ON or OFF
IP address is correct ✔

⚠️ If nameservers point to Cloudflare, do not manage DNS elsewhere.

—

🛠️ FIX 5: Clear Local DNS Cache

Sometimes the problem is local.

Windows:

$$
ipconfig /flushdns
$$

macOS:

$$
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
$$

Linux:

$$
sudo systemd-resolve –flush-caches
$$

Then restart your browser.

—

🛠️ FIX 6: Check If the Domain Exists

Make sure:

Domain is registered
Domain has not expired
WHOIS shows active status

An expired or suspended domain = DNS_PROBE_STARTED.

—

🧪 How to Confirm It’s Fixed

Open the site in incognito mode
Try from mobile data
Check from another location or device

If it loads → DNS is resolved ✅

—

⚠️ What This Error Is NOT

❌ Not a PHP error
❌ Not a WordPress/Flarum bug
❌ Not a server crash
❌ Not an SSL issue (usually)

It’s pure DNS.

—

📌 Summary

Error: DNS_PROBE_STARTED
Cause: DNS lookup failed
Fix: Correct nameservers + A record + wait for propagation
Risk: None
Difficulty: Easy

—

💬 Your Turn

Still seeing the error?

Which DNS provider are you using?
Are you using Cloudflare?
How long ago did you change DNS?

Post details below — we’ll help you fix it 👇

—

#dns #websiteissues #hosting #internetTroubleshooting