Skip to main content

Observe DNS Address Entry Conventions

One of the more frustrating steps involved in setting up a custom domain comes with entry of the DNS addresses, into the domain host or registrar's DNS dashboard aka zone editor.

Whether you are setting up a new domain, just purchased directly from a registrar - or re publishing an existing domain, purchased using "Buy a domain" - the addition of the proper DNS addresses is essential to successful custom domain publishing.

With some registrars, domain setup can be frustrating.

Sometimes, you just can't get the zone editor to accept the addresses, as provided by Blogger "settings instructions". Other times, you enter the proper values, your update is accepted by the zone editor - and the Blogger Publishing wizard rejects your attempt to publish.

Even after repeated attempts to publish your blog to the domain, you can get another "Another blog ..." error - maybe an "Error 12" or variant. You may not always see the anticipated "Error 12", if the domain does not properly point to Google servers.

You may see "Another blog ...", in spite of your efforts.

This may be in spite of the fact that you are retrieving a new "Name" / "Destination" periodically from "settings instructions", and dutifully adding or updating the domain ownership verification "CNAME" Alternately, you may just be adding the base DNS "A" or "CNAME" addresses.

There are syntax conventions, for both "Name" and "Destination".

Every blog owner needs to realise that the zone editors have conventions for entry of both the "Name" ("Label" / "Host"), and the "Destination" ("Target" / "Points To") values in the DNS address records ("Zone Entry"). The conventions used will vary, from zone editor to zone editor - and the differing conventions will affect the success of your domain publishing attempts.

How you enter the "Name" ("Label" / "Host") and "Destination" ("Target" / "Points To") values is essential to the success of the domain - and is not the same for all registrars. Even the terms "Name" ("Label" / "Host") and "Destination" ("Target" / "Points To") are not well defined. If you find this confusing, my apologies.

You may see the results of an error immediately, or later.

In some cases, the zone editor will immediately reject your entry, if you mis enter the value. In other cases, the entry will be accepted - but Blogger will reject your attempts to publish. Either scenario can be caused by mis entry of either the "Name" or "Destination" value, and your overlooking the differences between "absolute" vs "relative" addresses.

GoDaddy adds the trailing ".", in most cases!

This problem is observed by some as the mysterious "period" / "full stop".

  • If you omit the period, and it is required, the Zone Update may take place - but the Blogger Publishing wizard will overlook or reject the resulting DNS address. In some cases, the zone editor may try to verify the value - and reject your entry.
  • If you add the period, and it is not allowed, the zone editor will reject your attempt, as a syntax error.

Both the "Name" ("Label" / "Host") and "Destination" ("Target" / "Points To") values are subject to "absolute" vs "relative" address confusion.

The problem cannot be resolved by Blogger / Google.

Here, I will note that this problem is one which neither Blogger nor Google can resolve. Whether you purchased the domain using "Buy a domain" - or directly from the registrar - if you use the DNS dashboard / zone editor wizard provided by the DNS Host / Registrar, your understanding of the conventions observed by the zone editor are your responsibility.

You, the domain owner, must determine the syntax requirements.

There are requirements for entering the "Name" and for entering the "Destination" values - and you have to find out, and adjust to, each requirement.

For some zone editors, with a domain of "", you will probably enter the published address - "" - as "www". This says that the "Name" value is "relative" to the domain URL.

You can't enter the domain root, "", as "" - as this would give you a DNS address of "" - and yet another "Another blog ..." error. You will probably need to enter the domain root as "@" or a similar special character. This, too, is your responsibility to verify.

With other registrars, "" is entered as "". Nobody but the registrar can tell you which case affects your domain.

If you require assistance, be prepared to provide details.

If you are asking for help in Blogger Help Forum: Something Is Broken, and I am advising you, I'll be asking you for three essential values.

  1. The BlogSpot URL.
  2. The domain URL.
  3. The "Name" / "Destination" values provided by the "settings instructions" document, or "Error 12" et al display.

None of these values are optional - and strict attention to accuracy and detail, in your reply, is essential.

If you redact any portion of what you provide, I'll only ask you again, to not redact details. And I'll repeatedly advise you to always copy and paste - never type by eyeballing - both the long and short tokens ("Name" / "Destination") in the "Error 12" et al displays.


Rick said…
You have got to be kidding. Google is a multi-billion dollar company and they can't fix this most basic issue. I've tried eight times to move my blog to my own domain - which I've owned for 18 years - and all I get is further frustration. As a side note, I did this once before, about five years ago, and it was easy as pie and is still working.
Chuck Croll said…

Thanks for your observation.

Believe it or not, each registrar, not Google, determine their own syntax - based on how their domains and servers are setup, and how their zone editor works.

Google supports custom domain publishing, using domains served by every registrar able to provide the necessary DNS addressing. The syntax used by each registrar, in their own zone editors, is the business of each registrar - not Google.

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: