Skip to main content

The Blogosphere, And The Registrar Zone Editor

Sometimes, we see the frustration, in Blogger Help Forum: Get Help with an Issue, about custom domain setup.
I try to publish my blog to my domain, and I get
We have not been able to verify your authority to this domain. Error 14.
even when I know I have added the necessary DNS addresses. Why does Blogger ignore my addresses?
When we check, using multiple tools - such as DigWebInterface, or Kloth, or WhoIs, we see no addresses. Even, in some cases, when the blog owner is thoughtful enough to include well displayed copy of the zone editor display.

One of the biggest challenges in custom domain publishing involves registrars who use unique addressing syntax.

Any registrar is entitled to setup a zone editor, and use any label that they wish, to identify key domain settings.

  • Host Name ("Name" / "Label" / "Host").
  • Host Target ("Data" / "Destination" / "Target" / "Points To").
  • Latency ("Time To Live" / "TTL").
  • Record Type ("Type").

Note the different labels used - which exemplify the confusion.

Let's look at the Google Domains zone editor, as a reference.

Here's the Google Domains zone editor, for instance. The 4 x "A" + "CNAME" tag complement is pretty standard - but the labels and syntax, will vary, by registrar.

The "TXT" tag is my attempt to stay ahead of "SPF" email spoof filters.

The domain owner is responsible for determining the syntax used, in the zone editor provided by the registrar. If the domain owner gets the "Host Name" syntax wrong, and the zone editor adds a Host Name that does not match the host name needed, the "Dig" utility won't, intuitively suggest what host name to lookup.

This is similar to using a dictionary, to verify how a word is spelled. The "Dig" utility will only lookup the host name that is requested, using character by character matching.

If the domain owner adds the wrong host, while using incorrect syntax, all that we can learn from Dig is just what the Blogger dashboard Publishing wizard tells us.

There is no address for that host!


We have not been able to verify your authority to this domain. Error 14.

There is no Dig utility that will easily identify all hosts setup in a given domain. Many online Dig utilities have warnings, which forbid automated, persistent lookups.

Please do not abuse. No automated queries. No bots.

If you add a host to your domain, and 2 or 3 different Dig lookups do not find that host, it's up to you to contact a CSR at your registrar. Then, ask them what you did wrong, when entering the host Name and / or Target (under whatever label they use). Nobody can do this, for you.


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: