How to Fix “DNS_PROBE_POSSIBLE” Error on Blogger (2026 Step-by-Step Guide)
If you recently connected a custom domain to your Blogger website and suddenly saw the error “DNS_PROBE_POSSIBLE”, don’t panic. This is a common issue, especially for new blogs using custom domains.
In this guide, I’ll show you exactly why the error happens and how to fix it permanently, even if you’re a beginner.
What Does DNS_PROBE_POSSIBLE Mean?
The DNS_PROBE_POSSIBLE error means your browser cannot find the DNS records needed to load your website. In simple terms, your domain name does not yet know where your blog is hosted.
This often happens after:
- Adding a new custom domain
- Changing A Records
- Switching nameservers
- Recent DNS updates (propagation delay)
Common Causes of DNS_PROBE_POSSIBLE on Blogger
Here are the most common reasons:
- Missing or incorrect A Records
- Domain not fully propagated yet
- Wrong CNAME record
- HTTPS not fully activated
- DNS cache issue on your device
If you’re just starting out, you should read Beginner’s Guide to Learning Digital Skills before moving forward.
How to Fix DNS_PROBE_POSSIBLE Error on Blogger
Follow these steps carefully 👇
Step 1: Add Correct A Records
Make sure your domain DNS has all four Google A Records:
Copy code
216.239.32.21
216.239.34.21
216.239.36.21
216.239.38.21
Host: @
TTL: Automatic
These IPs point your domain to Google’s servers.
Step 2: Confirm CNAME Record
You must have:
www → ghs.google.com
This allows www.yoursite.com to work properly.
Step 3: Wait for DNS Propagation
DNS changes are not instant.
⏱ Normal wait time:
1–6 hours (sometimes)
Up to 24–48 hours (normal)
During this time, your site may:
Open on some devices
Fail on others
This is normal.
Step 4: Enable HTTPS in Blogger
Go to Blogger → Settings
Turn HTTPS Availability ON
Wait until status shows Available
Turn HTTPS Redirect ON
This helps Google index your site faster.
Step 5: Clear DNS Cache (Optional)
On Android:
Turn airplane mode ON for 30 seconds
Turn it OFF and reload the site
Or try another browser.
Google recommends submitting your sitemap through Search Console.
Does DNS_PROBE_POSSIBLE Affect Google AdSense?
Yes — temporarily.
AdSense requires:
- A working domain
- Stable DNS
- HTTPS enabled
Once your site loads normally and stays online, AdSense will work fine.
Final Thoughts
The DNS_PROBE_POSSIBLE error is not permanent. It simply means your DNS settings are still updating.
If you’ve added the correct A Records and CNAME, the problem will resolve itself within a short time.
Your blog will be live, indexable, and ready for growth 🚀

Comments
Post a Comment