Skip to main content

The GoDaddy Domain Manager: Removing An Address Entry

If you have a custom domain that was setup for you by Google Apps, or through the "Buy A Domain For Your Blog" wizard, or if you setup your domain to use the Google Apps standard configuration, you probably reference a Google server that doesn't exist any more. The Google server "" was taken offline some time ago, yet many custom domains still have this configuration. 3600 IN A 3600 IN A 3600 IN A 3600 IN CNAME

Reliance upon "" contributes to at least some of the cases of "Server Not Found Error 404" observed recently. If your custom domain contains a reference to that server, your domain will probably show these symptoms eventually. If your domain is already showing this symptom, that may be why you're here.

Removing the entry in question isn't difficult. Start from the GoDaddy Domain Manager, for your domain.

Find the entry under "A (Host)" for "". Look to the far right. See the 2 box icons under "Actions"? The one on the left is a pencil in a box ("Edit"), and the one on the right is an "X" in a box ("Delete"). Click on the box with the "X", in the row for "".

Next, click on "OK".

And, it's gone. 3600 IN A 3600 IN A 3600 IN CNAME

Much better for your domain, now.

>> Top


Thank you so much for this post about google server "". I went into my godaddy and account and deleted it successfully just now but my website is still down- since yesterday morning. I have a custom domain through blogger(, that I purchased through google apps in August '08. Now neither this site or my original blog address at is working. I am getting a "HTTP 404 - File not found" message for both.

Any other suggestions that you can think of?

Thanks so much again for your help. Louise
Chuck said…

Have you posted yet in GBH: Something Is Broken? The online forums are much easier to use, then Blogger Blog Commenting, for interactive problem solving.
Nancy Baird said…
Do you have to have an account with GoDaddy in order to do the above? I bought my custom domain from Google.
Chuck said…

If you bought the domain through Google, you start from an email from "google-apps-do-not-reply", setup your Google Apps account, then find instructions on logging in to eNom or GoDaddy, starting from the Google Apps dashboard.
Alex Chapman said…
Just a quick thank you for this post which helped me fix my blogger custom domain. The only other thing I had to do after deleting this A record was go to settings/publishing in my blog and switch back to blogspot, save, then switch back to custom domain/advanced settings, and put back in my domain. Not sure why this worked, but I was still getting a 404 before this, and after this (which I saw mentioned on the GBH Something is Broken forum) it now works. Thanks!

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: