Blogger website issue after nameserver update

What is the name of the domain?

advision.top

What is the error number?

1000

What is the error message?

DNS points to prohibited IP

What is the issue you’re encountering

my website appeared as Error 1000, DNS points to prohibited IP (Note: custom domain in Blogger). Pls help me to come out this issue

What steps have you taken to resolve the issue?

i tried out followings: To redirect your readers from “mydomain.com” to “www.mydomain.com,” set up a naked redirect:

Go to your domain provider’s website.
Open your DNS settings.
Add these 4 A-records that point to Google IPs. If A-records for “mydomain.com” already exist, you should remove the existing A-records.
216.239.32.21
216.239.34.21
216.239.36.21
216.239.38.21

What feature, service or problem is this related to?

DNS records

Screenshot of the error

Right now, I’m seeing an SSL handshake failure when I’m trying to open your site. Could you change your DNS records from proxied to DNS-Only for now?

Also, what DNS records are you supposed to use for Blogger?

here my original DNS once nameserver was updated

dear, please note that this happened after i updated new nameserver in namecheap from cloudflare.

I don’t know if Blogger works with proxied records. Google’s hosting service (GHS) does not, so I guess you might need to disable the proxy by changing your DNS records to DNS-Only.

no it worked but after this updating new nameserver this happened

Can you explain why you changed from an old Cloudflare account to a new Cloudflare account?

Did you copy all the DNS records from the old account? The automatic import wouldn’t work in that case.

1 Like

That screenshot is filled with Cloudflare proxy IPs that should never be present in the Cloudflare DNS app. Those A and AAAA records will need to be removed an replaced with values from the Blogger Guide.

2 Likes

Thankx, will see dude. But pls note that this is an issue of updating nameserver for existing domain already in Cloudflare & nt a 1st migration to Cloudflare

This:

Does not match this:

How come?

it came automatically after updating nameserver. here i updated what u all said but another issue appeared

If the IP addresses they provided you no longer work, you’ll have to check with them to find out what you should have in DNS.

If you’re using your full domain name as example.com and also want www, you should consider adding and using only CNAME setup.

My domain example.com is registered via 3rd-party domain registrar and actively using Cloudflare nameservers.

Nevertheless, when you add your custom domain or sub-domain, you’d get a pop-up message like below:

We were unable to verify our authority for that domain.
On the domain registrar’s website, find the Domain Name System (DNS) settings and enter the following two CNAME values: (name: cftest, destination: ghs.google.com) and (name: zdmvmakeler2, destination: gv-xxxxxxxxxxxxxxx.dv.googlehosted.com).
See Set up a custom domain - Blogger Help for detailed instructions.

In my case, I’ve used CNAME and sub-domain cftest.

Under the Blogger, you’d have to make some changes e.g.:

At Cloudflare DNS records:

Since the CNAME DNS records are proxied and :orange:, to make it work under the SSL/TLS settings you have to use Flexible SSL.

Or, in my case, since it’s sub-domain I’ve created a Configuration Rule under the Rules tab for my cftest sub-domain to use SSL Flexible:

At the beginning, before your domain or sub-domain is active with unproxied :grey: CNAME records, you’d experience either 404, or even for Flexible some 301 redirect (but with HTTPS enabled at Blogger), or if you’re having Full or Full (Strict) you’d have SSL handshake error.

Create your first page test and publish it, therefrom create your first blogpost and publish it as well.

slika

I can confirm my setup works fine, done in few minutes ago:

Later, add A www pointed to the 192.0.2.1 and proxied :orange: .

Using Redirect Rules under Rules tab, you can redirect www to non-www or sub-domain. Helpful article.

Regarding the SSL issue for Google, you might have some issue getting it at first if you’re using some Custom Rules for WAF since Google Certificates would try to request an SSL for your (sub)domain:

no one dont know how to resolve this ??? :thinking: :thinking: :thinking: :thinking: :thinking:

See my post from above. Go with CNAME setup as guided. Add your example.com without www to Blogger as custom domain. Later you can setup redirection from www to your example.com at Cloudflare and add another alternative sub-domain (even the www) in the Blogger settings alongside the custom (sub)domain.

Please read the previous two responses, and let us know the specific results of checking with your host, as well as the above settings.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.