Some time ago, I wrote about blogs, newly setup for custom domain publishing, undergoing a transition period, where both the Blog*Spot and Custom Domain URLs are active, but seemingly 2 separate web sites. This appears to be a (almost exactly) 72 hours while Google allows time for DNS propogation of the new URL to take effect, worldwide.
Now, it appears that some blogs, having gone through the transition period, are still not active.
Here's one case, "keith-in-training.com".
keith-in-training.com. 3600 IN A 64.233.179.121
keith-in-training.com. 3600 IN A 66.249.81.121
keith-in-training.com. 3600 IN A 72.14.207.121
www.keith-in-training.com. 3600 IN CNAME ghs.google.com.
Appears to be a normal, asymmetrical DNS setup made using either "Buy A Domain" or maybe Google Apps.
5/31/2008 19:52:36 Trying http://keith-in-training.blogspot.com
Redirect!
Header:
HTTP/1.0 301 Moved Permanently
Location: http://www.keith-in-training.com/
Content-Type: text/html; charset=UTF-8
The Blog*Spot URL redirected, by "301 Moved Permanently", to the custom domain "www" alias.
So far, so good.
But wait - there's more!!
No!! The whole URL is down, now.
One step forward, another back. But remember, this is a known symptom. If you are seeing the above display (but only the above display):- Publish the blog back to it's previous Blog*Spot URL, then republish to the custom domain URL.
- If you get the old "Another blog ..." error, recycle your Google Apps settings.
- Please, leave a comment here with your Blog*Spot and custom domain URLs, and whether or not the above procedure was successful.
>> Top
A couple of weeks ago, I published Custom Domain Publishing, And The 404 Error - Chronic Edition. Since that time, I was able to contact Blogger Support more directly than through this blog, and I was able to pass on to them a few egregious cases which included the symptoms described in that post. Several of those cases, they were able to ultimately fix.
Many people were happy. Kudos, Blogger.
Until today that is; when 2 people, who were earlier using their blogs quite happily, reported to me, within the span of 1 hour, that their blogs were, now, displayingServer Not Found
Error 404
Note, please, that the error, previously reported, was not identical.Not Found
Error 404
Not Again!!
What does this mean? Only Blogger Support can say for sure.
If your custom domain published blog is now showing this new symptom, please let us know. Comments will be posted below.
Problem Log
| Date | Domain | Remarks |
| 5/14 | deliverancegothic.com | - |
| | mycup2yours.com | |
| 5/15 | fragrancediva.net | |
| | greateststorytold.com | |
| 5/19 | robjessica.com | |
| 5/23 | lloydclaycomb.com | |
| | yangor.com | |
| 5/29 | shriramamgroup.info | |
| | jetaaqld.org | |
| | gabrielcusac.com | |
>> Top
For some time now, blogs published to a custom domain, and previously working, have been (apparently) randomly yielding a new monolithic error when being read.Not Found
Error 404
Recently, owners of blogs supposedly not associated with custom domains have complained of this oddity also.
Why not at leastThe blog you were looking for was not found.
or maybe evenBlog not found
Sorry, the blog you were looking for does not exist. However, the name xxxxxxx is available to register!
If your BlogSpot blog, not now and never previously part of a custom domain, is showing this symptom, please comment here with the blog name. If you're suffering from this idiosyncrasy, silence won't get the problem fixed.
>> (Update 5/28): Blogger Support has suggested a possible (distant) connection between template corruption and observation of this symptom.
>> Forum thread links: bX-*00080
>> Copy this tag: bX-*00080
>> Top
On the surface, the old "404 Not Found" would be one problem - simply your computer saying "Hey! I can't access the other computer!". Those of us who work in computer and network troubleshooting know that there are dozens of possible causes for that one symptom.
We know, for a certainty, that if we persist in believing that there is one problem causing all of the "404 Not Found" errors, that one problem will never be solved. This symptom will be solved only with detail and determination, and lots of diagnostic work.
>> (Update: 5/18): Blogger Support is now suspecting a link between use of Google Apps, and the 404. If you are having this problem, please help us diagnose the problem. Describe your use of the following Blogger / Google applications / wizards, with any possible details (relevant dates would be useful), in setting up or maintaining your domain:
>> Forum thread links: bX-*00077
>> Copy this tag: bX-*00077
>> Top
The problem of blogs, published to a custom domain, suddenly returning a "404 Not Found" when access is attempted, has been chronic since November 2007. Almost daily, we'd see reports of 2 or 3 such problems.
This evening, we saw 4 reports in a space of 1/2 hour. And we continue to see more.
The good news is, so far the reported cases all respond favourably to having the blog published back to BlogSpot, then republished to the "www" alias, using "Advanced Settings". In some cases, the victims have reported success after repeating the republishing cycle.
>> (Update: 5/18): Blogger Support is now suspecting a link between use of Google Apps, and the 404. If you are having this problem, please help us diagnose the problem. Describe your use of the following Blogger / Google applications / wizards, with any possible details (relevant dates would be useful), in setting up or maintaining your domain:
>> Forum thread links: bX-*00076
>> Copy this tag: bX-*00076
>> Top
