Skip to main content

Custom Domains Do Not Always Need Ownership Verification

We're seeing a new source of confusion, in Blogger Help Forum: How Do I?, with blog owners trying to publish to a custom domain URL.
How do I get my second "CNAME"?
The Publishing wizard does not, always, provide instructions for ownership verification - and some owners don't understand that ownership verification is only necessary when it's demanded.

When ownership verification was first introduced, whenever a blog owner would use the Publishing wizard, to publish or re publish to any non BlogSpot URL, every use of the wizard would involve creating a new ownership verification "CNAME".

The ownership verification "certificate" is unique to both the URL being published, and the time the publishing takes place. If the owner waited too long between publishing attempts, a new "CNAME" would be again demanded. If multiple hosts were published in a domain, multiple "CNAME"s were required.

In some cases, each domain address being added would require at least 2 "CNAME"s - the DNS address for the published host (""), and the ownership verification (the long, random text). Domains with multiple hosts would end up with multiple, redundant, and useless ownership verification "CNAME"s.

Later, Blogger changed the requirement, so only one verification was required, for the domain.

Each domain now has an ownership verification indicator, invisible to us. If ownership is verified once, that is generally enough. When you publish to a domain URL, either a verification "CNAME" Is required, or it is not required.

In some cases, trying to Publish to a domain URL, with bogus base DNS addresses, will generate another infamous "bX" code - or the blog will seem to publish, but may be offline when accessed. Upon correction of the problem, with righteous DNS addresses setup, the Publishing wizard will simply publish, and the domain will be operational.

In either case, no second "CNAME" will be required. When the domain is operational, you wait for domain propagation (formerly called "Transition") to complete. While waiting, you continue the migration.

When the migration process is complete, you get on with publishing the blog.

If it should be necessary to re publish to the same host, or publish to a different host, in the domain - and ownership verification is required, instructions for adding a new "CNAME" will be provided. When the new "CNAME" Is needed, the new verification address (again, sensitive to domain address and to time of request) will be displayed in the Publishing wizard.

If ownership verification is not required, and the domain becomes operational when the Publishing wizard is used, you are done.

Some owners will use Google Webmaster Tools, and manually generate an ownership verification. This will give you specifications for a "CNAME" / "TXT" that is unnecessary now - and later, will be out of date. And, if your domain zone edit file is limited in size, this will unnecessarily limit the number of hosts you can add.

Helpful instructions by Blogger not withstanding, you need to add righteous DNS addresses, and get the domain working.

If ownership verification is required, add the required "CNAME". If ownership verification is not required, finish the domain migration, then get on with publishing the blog.

>> Top


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: