Up to now, if you wanted a blog (web site) named myblog, you had 2 choices.
- Setup myblog.blogspot.com, hosted by Blog*Spot, and with all of the shiny features of (now) New Blogger.
- Setup myblog.com (myblog.org, ...), hosted by a host of your choice (and extra cost in most cases), but with less features than a Blog*Spot hosted blog.
Note: This post has been migrated (and significantly enhanced) as The Real Blogger Status: Custom Domain Names Hosted By Blogger.
Now, there is a third choice. Setup myblog.com (myblog.org, ...), hosted by Blog*Spot.
- You pay for the DNS listing, which tells your reader's computers where your blog is.
- You setup a DNS entry, pointing "myblog.com" to "ghs.google.com".
- You setup Blogger to publish to the custom domain.
This solution has its good, and its bad, points.
- The Good:
- Save money. No need for an extra cost hosting service.
- All of the shiny features of New Blogger.
- None of the unstable publishing problems, reported of late.
- Your current Blog*Spot address will continue to work, and to forward to your new, custom domain.
- No more abandoned Blog*Spot address, and no more subsequent splog hijackings.
- The Bad:
- If you opted for external publishing to get away from Blog*Spot hosting, this isn't for you.
- If your domain contains more than a blog - ie maybe a chat room or FTP server, this may be a problem. You have two possibilities here.
- Have two named domains - one inside Blog*Spot, the other outside, and links between the two.
- Setup a subdomain DNS record, pointing to "ghs.google.com". Make sure that all of the links between the website and the blog are absolute, ie "http://myblog.mydomain.com", rather than "/blog".
(Note 1/16): There's a lot of theory here. See Google Custom Domain - Case Study #1 for an actual exploration of the facts. And see Setting Up A Custom Domain? Here's Advice, for a review of the essential steps that you must follow.