Skip to main content

Copy And Paste The Ownership Verification Details

The Custom Domain Ownership Verification requirement has been with us for over a year - and we still see confusion, and easily corrected mistakes.

One of the most frustrating mistakes involves mistyping of the details.
I keep getting an "Error 12". My registrar insists that the DNS addresses are right.
But, the registrar must be wrong, since the blog just can't be published!

When you type the base domain DNS addresses, into the registrar's zone editor, eyeballing what you type is somewhat obvious. Either you get it right - or you don't. Typing the domain ownership verification details, on the other hand, is not so simple.

When you setup your domain, you know the domain name. Who's buried, in Grant's Tomb, anyway?

You probably spent hours, choosing just the right domain name. Choosing an available, yet memorable, domain name is not a simple task. Some consultants make the domain name an essential, initial choice, in setting up a company.

Since you know the domain, when you setup the base DNS addresses, it's reasonably easy to get that right. Having gotten the base DNS addresses setup just right, you try to publish the blog to the domain - and now you get the infamous "Error 12".

An example of the "Error 12" display.
See the short, and long, tokens?

The problem with the "Error 12" is not just having to setup one more DNS address. You already setup 2 - or maybe 5 - to get the base DNS addresses. The big problem here is the content of this second "CNAME".

You know every character of the base DNS addresses. You've typed all of that, over and over. Then, you look at the second "CNAME" - which contains pure random garbage.

Pure random garbage that is essential, on a character by character basis. Get just one character wrong - or omitted - or reverse any characters, in sequence - and the "Error 12" never goes away.

  • The “Name / Label / Host” value ("short token") is exactly 12 characters.
  • The Destination / Target / Points To” random value ("long token") is exactly 14 characters.
  • Do not confuse a “O” / “o” (alphabetic characters) with a “0” (numeric character).
  • Do not confuse an “l” or "t" (alphabetic characters) or a “1” (numeric character).
  • Do not confuse a "w" (single, alphabetic character) with a "vv" (two alphabetic characters).

Do you have a good quality magnifying glass handy? Use it - and look at the differences and similarities, in the above 5 cases used above, as examples.

When you get an "Error 12" or similar, and the message includes a section
Name, Label or Host field Destination, Target or Points To field
The only proper procedure here involves use of the clipboard. Copy / paste the short token, then copy / paste the long token.

Don't type by hand. Please. And when you copy then paste, keep in mind the zone editor entry syntax, which is essential to a working domain - and differs from registrar to registrar.


The New life said…
Hi, please how do you add the 2nd CNAME to hostgator? Can we communicate via email still trying to sort out my domain transfer from hostgator to blogger

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: