Skip to main content

Google Does Not Provide DNS Services

When you setup a Google Custom Domain, so you can publish your Blogger blog to a non-Blog*Spot URL, Google continues to host the blog content.

Your readers, and you, access the blog content using the URL of the blog, and require use of the DNS system to do that.

However, Google doesn't host the DNS, and DNS hosting is an essential part of the custom domain setup process. Lack of proper DNS setup, for your custom domain, may cause any of several results - none of them good.

Custom domain publishing sets up 3 links, within the Google domain database.

When you publish your blog to a custom domain, you're setting up 3 links within Blogger / Google.
  1. All internal blog links, such as the blog feed URLs, and all links from any part of the blog to the others, are converted to point to the custom domain URL.
  2. A "301 Moved Permanently" redirect is setup for the original BlogSpot URL, pointing to the custom domain URL.
  3. An entry in "ghs.google.com" is added, pointing the custom domain URL to the blog.

All 3 of those links are purely within Google. For any, or all, of those links to work, you have to have a DNS entry for the custom domain URL, defined outside Google, pointing to Google.

With the domain successfully published, you can setup a secondary URL.

When you get the blog successfully published, you can optionally define a second URL to address the blog. If you published the blog to "www.mydomain.com", you can select "Redirect mydomain.com to www.mydomain.com.", and "mydomain.com" becomes an secondary URL. Here too, the Redirect is purely within Blogger.

You will have to have a DNS entry for the redirected URL, defined outside Google, pointing to Google.

If you're going to select "Redirect www.mydomain.com to mydomain.com.", you have to have properly setup DNS entries for both "mydomain.com" and "www.mydomain.com", and these entries must point into Google. If you don't have both URLs defined, or if both entries don't point into Google, you can expect to see a dear old friend
Another blog is already hosted at this address.

If you get the latter error, you either won't be able to publish the blog to the custom domain, or you won't be able to redirect the secondary alias. And that will possibly bring you to a second dear old friend
Not Found

Error 404
or possibly
Forbidden

Error 403

The errors discussed can have multiple causes - including incorrect DNS.

Both errors - "Another blog is already hosted at this address." and "Not Found Error 404" / "Forbidden Error 403" - can have multiple causes. If you see either error, it may not always cause / be caused by the other, and neither will be exclusively caused by bad DNS. But if you don't get your DNS setup properly, you can count on seeing one or both.

When you see "Another blog is already hosted at this address.", and it's caused by bad DNS, you will have to diagnose and fix the DNS problem, before you can reset the problem in Blogger. Whether you're using the Custom Domain Reset form, or the Google Apps domain setting recyle procedure, you have to get the DNS setup properly, first.

Don't waste your time, get your DNS working. DNS hosting is an essential part of the custom domain setup process.

Comments

Hi

I've read, I suppose carefully, everything you've written...

I registered one domain on one Portuguese registrar matematicaviva.pt and I wanted it to point to my blogger webpage...

I've done everything you have said.

I configured my DNS assymetrical, as it is in google help page, though, www.matematicaviva.pt works, but the naked matematicaviva.pt (no www) doesn't seem to work...

I've done everything and it doesn't work!

Can you kindly help me?

Best regards

João
Nitecruzr said…
João,

I'll try to help, but I can do this a lot better from Blogger Help Forum: Something Is Broken.
Unknown said…
I wish to use http://www.parasitech.net as my custom domain for my blog at http://parasitech.blogspot.com/ . My domain registrar does not allow me to change or modify the Cname. I have to write to them to do it for me. Here I would like to know how do I proceed setting up stuff.
Nitecruzr said…
I wish to use http://www.parasitech.net as my custom domain for my blog at http://parasitech.blogspot.com/

Salil,

This is an excellent question for you to ask in Blogger Help Forum: How Do I?, where we can have a dialogue.

Popular posts from this blog

Embedded Comments And Main Page View

The option to display comments, embedded below the post, was made a blog option relatively recently. This was a long requested feature - and many bloggers added it to their blogs, as soon as the option was presented to us. Some blog owners like this feature so much, that they request it to be visible when the blog is opened, in main page view. I would like all comments, and the comment form, to be shown underneath the relevant post, automatically, for everyone to read without clicking on the number of comments link. And this is not how embedded comments work.

What's The URL Of My Blog?

We see the plea for help, periodically I 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?".

With Following, Anonymous Followers Can't Be Blocked

As people become used to Blogger Following as just another tool to connect people, they start to think about the implications . And we see questions like How do I block someone who's been following my blog secretly? I couldn't see her in my Followers list (hence I couldn't use the "Block this user" link), but I have looked at her profile and could see that she's Following my blog. Following, when you look at the bottom line, is no more than a feed subscription and an icon (possibly) displayed on your blog, and linking back to the profile of the Follower in question. If someone Follows your blog anonymously, all that they get is a subscription to the blog feed. If you publish a feed from your blog, and if the feed is open to anybody (which, right now, is the case ), then it's open to everybody. If someone wants to use Following to subscribe to the feed, you can't stop this. You can't block it before, or after, the fact. You can't Block w