Skip to main content

Setting Up A Custom Domain

Having written my referential guide Troubleshooting Your Custom Domain Problems, I have seen more than a few questions in Blogger Help Forum: Something Is Broken that are solved by use of the guide. Maybe you can avoid use of that guide, if you plan ahead of time.

The vast majority of all bloggers, when seeking to publish their blog to a custom domain, will do quite well to use the "Buy A Domain For Your Blog" wizard.
  1. Have a major bank issued credit card, for an account that's in good standing, in hand.
  2. Pick an available domain.
  3. Provide the credit card information.
  4. Get the email from Google Apps.
  5. Setup your new Google Apps account.
  6. Get to work planning and managing the transition to the new URL.
  7. If you just completed step #6, please skip to the end of the article, now. What's below is not your concern.

As of 2013/06/23, "Buy a domain" is no longer offered, as part of "Add a custom domain".
Maybe you can't use "Buy A Domain", for your purchase.If you're in this group, I suggest that you plan the setup process, and similarly, the domain renewal options. Save yourself (and us) a lot of headache, by considering the details, before you purchase.
  1. Choose a registrar that will provide the proper DNS services, and the required support. Even if you cannot use "Buy A Domain", you may do well to use eNom or GoDaddy as your registrar, if possible.
    • We are more familiar with their procedures and wizards. We can provide corrections, for well known problems.
    • Their CSRs are becoming increasingly familiar with needs of Google Custom Domains.
    • We are reasonably certain that they are able to provide the necessary services.
    • As a GoDaddy customer, you can use the Blogger / GoDaddy "Update your DNS records" wizard, to setup your DNS, after your domain is registered by GoDaddy.
    It's your choice, but you can make it easier for yourself, and for us.
  2. Setup the DNS addresses properly, using one of three models. For details, please see:
  3. Re publish the blog to the new domain. Select the "Redirect" option (if desired). Note that even if you do not (or cannot) redirect one URL to another, using one of the three models is seriously recommended.
  4. Setup a new Google Apps account (if necessary).
  5. Get to work planning and managing the transition to the new URL.

This is simple advice, but it will be worth your while to understand the requirements, and to execute the details, religiously. Custom domains are very simple, in concept - but if you set one up wrong, you can have all sorts of problems.

Get it right, from the start. Make it easier, for everybody.

>> Top


Amy said…
Hi. Are you saying that if my client registered his domain through the Blogger interface that he is NOT ABLE to now switch hosts because no access is granted to the DNS settings?
Chuck said…
I don't think so, Amy. If your client registered his domain through the Blogger interface, he'll need the email from Google Apps, which will give him access to setup an Apps account, which will give him instructions and access to eNom / GoDaddy.
seowebmaster said…
no, that's not correct. it does not matter where you purchased your domain? it is the game of setting dns on your domain control panel
Chuck said…
it does not matter where you purchased your domain

All registrars being equal, it should not matter. But all registrars won't be equal.

Every different registrar has different policies, and a different Control Panel. Not all registrars allow "CNAME" referral, or "4 x A" referral for the domain root.

So no, all registrars are not equal, and it does matter where you purchased your domain.
Kanchan said…
I really need to... actually i creat a blog name now i want to host my own custom domain on it, which i purchased from
how can i do it... please tell me
Kanchan said…
i Have purchased from please help me to host it with blogger blog
Ed said…
I have a .us domain name with Godaddy. Can I use blogger to host my .us domain? Google Blogger only allows 5 domains: .com .net .org .info and .biz. All other domains are not supported. Thank you.
Chuck Croll said…

If you use "Buy a domain", you will be hosting a blog with either eNom or GoDaddy - Blogger does not host domains, period.

You can't use "Buy a domain" to purchase a .us domain. You can only use "Buy a domain" to purchase a ".com", ".net", ".org", ".info", or ".biz" domain.

If you want to purchase a ".us" domain, you will have to purchase it directly from eNom, GoDaddy, or any other registrar. Having purchased the domain, please set it up properly.

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: