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.
Chuck Croll 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

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: