Skip to main content

Confusion Over Custom Domains Using AdSense For Domains DNS Servers

I've been warning people for years about the lack of detail provided by Google, in their instructions about setting up a custom domain, with the domain registration purchased directly from a registrar
.... you only need to get the domain name; you don't have to pay extra for hosting service.
That was an observation, that I made, 5 years ago.

The Google provided instructions were recently changed - unfortunately, not to satisfy every new domain owner's need for detail. Recently, we're seeing new evidence of confusion - which appears to start with Google instructions, again.

As I have written repeatedly, when you setup a private domain, to use in publishing a Blogger blog, Google does not provide DNS hosting for your private domain. Recently, I learned about the AdSense for Domains DNS servers.
Apparently, some people have been able to use the AFD DNS servers to provide DNS hosting for their private domains.

This week, we're seeing reports in Blogger Help Forum: Something Is Broken from some unhappy blog owners.
Beginning last night, every time I try to view my blog, "", I get the msg "Server not found". Why is this happening?
Starting with a Who.Is lookup of "" (in this example), we see:


Whois Server:
Referral URL:
Status: clientTransferProhibited

Expiration Date: 2014-03-21
Creation Date: 2012-03-21
Last Update Date: 2012-04-07

Name Servers:
And there we see, as mentioned above:

In this example, "" was, apparently, setup originally to use "" (x 4) for domain DNS addressing. Apparently, until this week, the addressing worked - and Google was willing to host DNS addressing for some private domains.

Now, it doesn't.

Looking at the content of AdSense Help: Pointing your domains to Google's servers, we see the warning
Hosted domains has gone away. AdSense stopped supporting Hosted domains on April 18, 2012.
Apparently, "gone away" means that the AFD DNS servers "" (x 4) are now offline.

Opening a Command Window in Windows, we get confirmation

Pinging [] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
So, there you have it - "" (x 4) is apparently offline. Once again, there is no free lunch. Read - and heed - the fine print.

If your domain was using those servers to serve DNS addresses, you're going to have to go back to your registrar, and ask them for their DNS servers. If this involves changing your "Name Registration" service to "DNS Hosting", you're going to have to bear the cost.

>> 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: