Skip to main content

Custom Domain Publishing, And "403 Forbidden"

Next to its immediate cousin error
Another blog is already hosted at this address
I don't know of too many more frustrating Blogger error states than seeing
403 Forbidden
Most cases of "403 Forbidden", seen and discussed recently in Blogger Help Forum: Something Is Broken, have geographical affinity - and are typically transient - and apply to blogs published to "".

Some cases of "403 Forbidden" however, will involve custom domain publishing, where the blog owner should - but most likely will not - see
Another blog is already hosted at this address
When publishing the blog to the domain.

In some cases, when publishing a blog to an incorrectly setup custom domain, the custom domain publishing wizard will fail to detect the incorrect DNS addresses. Instead of the blog owner, seeing immediately
Another blog is already hosted at this address.
The owner will see
Your blog has been published.
Later, the blog owner - and all potential blog readers - see the secondary symptom
403 Forbidden

Here, we have an excellent example of the problem - diagnosis, and treatment.

Let's first look at a Dig log extract.    86400    IN    A 86400 IN    A

Now, an HTTP trace extract, showing unsuccessful access to the domain.
Sending request:

GET / HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1
Connection: close

• Finding host IP address...
• Host IP address =
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
The solution to this problem involves a standard misconfigured domain diagnosis (excerpted here), and requires DNS address correction.
Here's what you have: 86400 IN A 86400 IN A

Google custom domain publishing requires properly setup referrals to Google servers. "" is not a Google server.

Here's what you need: 86400 IN A 86400 IN A 86400 IN A 86400 IN A 86400 IN CNAME

>> Top


Anonymous said…
I have followed the steps yet, still no give. I use fatcow and have managed to previously route my blog for a second. However instead of I recieve I called fatcow and they said it's google's problem. I have no idea what to do, I'm loosing tons of traffic that I have built up, due to the errors.
Nitecruzr said…

You're reporting a Start Page redirect, which is similar to a Sites redirect. If the linked article does not give you enough details, please post a report in Blogger Help Forum: Something Is Broken

Popular posts from this blog

What's The URL Of My Blog?

We see the plea for help, periodicallyI need the URL of my blog, so I can give it to my friends. Help!Who's buried in Grant's Tomb, after all?No Chuck, be polite.OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Leave Comments Here

Like any blogger, I appreciate polite comments, when they are relevant to the blog, and posted to the relevant article in the right blog. If you want to ask me a question thats relevant to blogging, but you can't find the right post to start with (I haven't written about everything blogger related, yet, nor the way things are going I don't expect to either), ask your questions here, or leave an entry in my guestbook.

As noted above, please note my commenting policy. If you post a comment to this post, I will probably treat it as a "Contact Me" post. If you have an issue that's relevant to any technical issue in the blog, please leave a comment on the specific post, not here. This post is for general comments, and for non posted contact to me.

If the form below does not work for you, check your third party cookies setting!

For actual technical issues, note that peer support in Blogger Help Forum: Something Is Broken, or Nitecruzr Dot Net - Blogging is, almos…

What Is "" vs. ""?

With Google Domains registered custom domains becoming more normal, we are seeing one odd attention to detail, expressed as confusion in Blogger Help Forum: Learn More About Blogger.My website uses "" - am I supposed to use "", instead?It's good to be attentive to detail, particularly with custom domain publishing. This is one detail that may not require immediate attention, however.