Paul F Burgueño

It has hosted another blog at this address - Part II

In the last two weeks I have received three requests to go a bit deeper in the explanation of the solution to this error message from Blogger:

" We have already hosted another blog in this direction . "

I'm not the only one who has encountered this problem so you can also read solutions and comments:

• Wolo
• Technobichos
• Google Groups (in English)

At its most abstract, the problem is solved in four steps:

1. Change the CNAME your domain to www. and write it to ghs.google.com
2. You turn off the service with Google Apps web pages and then publish a test page.
3. After viewing the test page, off again web service.
4. Now point the blog to the desired URL. No longer will the mistake of "stay another blog."

But if you've already lost, because you need to first understand the reason for the failure.

When you create a Blogger blog on what you actually do is add content to a template that will be hosted in a subdomain of "blogger.com".

In other words, you create a page within blogger.com. What happens is that instead of putting "www" in front (thus being "www.blogger.com"), you put a name chosen by you, for example, "informaticaycomunicacion.blogspot.com." What we are doing is modifying the initial part of the domain name: we are creating a subdomain. The full name (or informaticaycomunicacion.blogspot.com www.blogger.com) is denominia DNS. The DNS URL is preceded by "http://", ie "http:// + DNS"

So far we have is a blog hosted on a domain that does not belong to us.

If we buy a domain for our blog (eg ley20.com ) we can link the blogger's DNS so that instead of that, leave ours. But might also consider the following configure error: "We have already hosted another blog in this direction."

Why? This occurs when newly purchased our address is already used by some service related to Google.

How can this be? In my case, had activated minutes before Google Apps for your domain ley20.com as Google (Blogger is Google) it was believed that there was already a blog hosted in that direction.

The association between your blog and recently bought the domain is from the domain control panel, changing the CNAME. The panel is different depending on what provider you have sold, but the place to make that change often coincides with the following guidance: "Domain Settings / Configure DNS / CNAME". The CNAC is precisely the association information is made between a given DNS and a destination, the first of where they take the text for the URL and the second where you get the content of the website or blog destination. This association must be done specifically targeting ghs.google.com.

What I can do If your case is that of Google Apps, just completely disable that service (as indicated above, in the four points) and start again. Google Apps may take up to five days in disabled, but not likely. Instead, it is very likely to leave you a new error (the famous 404), but quiet, disappears in 48 hours.

A 404 error or page not found, appears in this case because the logs (automatic quick reference files that store last movements) were not yet updated so that the order to show your actual page conflicts with a statement date. This causes the server does not find your blog. The instructions of the log normally renewed every 48 hours.

If your case is not that of Google Apps, then there is another Google service that is using your DNS. This can only happen if you previously configured the CNAME to point to ghs.google.com. Devánate brains until they remember what you have on and then turn it off! and complete the configuration of your domain.

So far, the explanation of how to fix the error It has hosted another blog in this direction. For explanations on how to modify the DNS, how to configure the domain, how to create subdomain or how to toast bread: Google

Update: Blogger form to solve this problem within 24 hours