A Blogspot/eNom scenario to watch out for

by Maskil on 2 Jul 2008

Just something to watch out for if you’re:

  • Setting up a new blog on Blogger/Blogspot
  • Using a custom domain name rather than a Blogspot address
  • Purchasing your domain name through Google Apps/eNom
  • Naming your blog “blog.yourblog.com” (or presumably anything except www.yourblog.com

OK, when you put it like that, it doesn’t look like a scenario that will affect many other people, but I’ll share my experience anyway! Here’s what happened, as per my topic on the Blogger Help Group:

I created the following blogs on Friday, 27th. I also purchased custom domain names for them through Blogger/eNom.





I would have expected the custom domain names to be “live” by now [Monday, 1 July 2008]. Instead, I’m getting a Page Load Error, as follows:

Page Load Error


Address Not Found

Firefox can’t find the server at blog.j-blogosphere.info.

The browser could not find the host server for the provided address.

* Did you make a mistake when typing the domain? (e.g.

“ww.mozilla.org” instead of “www.mozilla.org“)

* Are you certain this domain address exists? Its registration

may have expired.

* Are you unable to browse other sites? Check your network

connection and DNS server settings.

* Is your computer or network protected by a firewall or proxy?

Incorrect settings can interfere with Web browsing.

I’m unable to logon to eNom to check the settings there (from what I understand, this shouldn’t be necessary anyway), as no logon details for eNom have been provided.

This also appears to be causing issues with both Windows Live Writer and ScribeFire ITO publishing posts and recognizing the theme of the blog.

How do I go about getting this sorted out?

After reading my confirmation messages from Google Apps thoroughly, I was able to resolve the issue myself, as follows:

Problem appears to have been resolved. Thanks in advance.

Apparently the CNAME for the chosen hosts (“blog” in both cases) is NOT automatically generated, although the interface gives one this impression. I needed to sign on to Google Apps and access my DNS Settings from there.

Presumably it would have worked if I’d selected “www” as the host, as that default CNAME does exist.

So there you have it. The custom domain name workflow appears to assume that you will be naming your blog using the “www” prefix. If you’re not, it’s up to you to ensure that you set up the appropriate CNAME record; a breeze using the interface provided.

I hope someone else out there will benefit from my experience!

Page Load Error – Something Is Broken | Google Groups

Previous post:

Next post: