One of the most well known, and resented, shortcomings of the Google Custom Domain product has always been the inability to have your blog respond to both "www.yourdomain.com" and "yourdomain.com", simultaneously.
Bloggers have been requesting, and waiting for, this shortcoming to be corrected constantly, since January 2007, when Custom Domains was released.
Today, I idly went to check the Settings for one of my blogs, that's published to a Custom Domain. What did I happen to spot?
Surprise!!!
Now to find a way to test it, and hopefully make it work??!!
Obviously, we need to start with both "martinezumc.org" and "www.martinezumc.org" hosted by Google.
So now, the rubber must meet the road.
Dang!
And as normal, what looks like yet another flat tire. But think again. That's just the old monolithic error, which has a tested workaround.
Half an hour of perplexed meandering through Google Apps, and ...
Success!
One small step forward.
>> Top
Bloggers have been requesting, and waiting for, this shortcoming to be corrected constantly, since January 2007, when Custom Domains was released.
Today, I idly went to check the Settings for one of my blogs, that's published to a Custom Domain. What did I happen to spot?
Surprise!!!
Now to find a way to test it, and hopefully make it work??!!
Obviously, we need to start with both "martinezumc.org" and "www.martinezumc.org" hosted by Google.
C:\>ping www.martinezumc.org
Pinging ghs.l.google.com [64.233.179.121] with 32 bytes of data:
Reply from 64.233.179.121: bytes=32 time=75ms TTL=247
Reply from 64.233.179.121: bytes=32 time=73ms TTL=247
Reply from 64.233.179.121: bytes=32 time=75ms TTL=247
Reply from 64.233.179.121: bytes=32 time=72ms TTL=247
Ping statistics for 64.233.179.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 75ms, Average = 73ms
C:\>ping martinezumc.org
Pinging ghs.l.google.com [64.233.179.121] with 32 bytes of data:
Reply from 64.233.179.121: bytes=32 time=70ms TTL=247
Reply from 64.233.179.121: bytes=32 time=76ms TTL=247
Reply from 64.233.179.121: bytes=32 time=75ms TTL=247
Reply from 64.233.179.121: bytes=32 time=71ms TTL=247
Ping statistics for 64.233.179.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 76ms, Average = 73ms
So now, the rubber must meet the road.
Dang!
And as normal, what looks like yet another flat tire. But think again. That's just the old monolithic error, which has a tested workaround.
Half an hour of perplexed meandering through Google Apps, and ...
Success!
One small step forward.
>> Top
Comments
btw, thanks for being so diligent about updating this blog. i simply don't have the time i once did to frequent the help forum, and my own blogs work fine ("if it ain't broke..."), but it's good to at least be informed of developments.
Yeah right Chuck. As if any of the church members would notice.
Anyway, thanks for the feedback. It's definitely a boost to have you commenting, if ever so briefly. The forums (you know which ones, too) are a bit poorer without you. Your membership is still there.
I try to re-read through all your posts as regard to this matter which often mention to disable Google Apps which i don't understand. I use free Google Apps to host my email, is this the same Google Apps we're talking about? How to disable that Goggle Apps? Should i disable my email? I did this once to my other domain and i never ever successfully re-added the domain to GA.
So i'm confused. I think the new redirect custom domain feature will mislead many bloggers. Earlier today i thought i was the only one.
Please help me. Seems like noone working at Blogger except robots.
I'm working on a more complete article, with lots of pictures, on how to use Google Apps to reset the problem. I think you'll be easier to help, if you'll post in Google Blogger Help, where we can converse easier.
Please recycle the domain settings, using Google Apps.