A Tale Of Two Domains
Blogger rolls on, and upgrades their product in silence. Here we see another example of that process.
We're going to examine two blogs - MartinezUMC and ToaCx4. We'll start with excerpts from the ever useful DNS Report, provided (free) by DNS Stuff.
martinezumc .org
The relevant portion of the DNS Report for the domain for my church blog, previously examined in my Case Study #2.
toacx4 .info
The relevant portion of the DNS Report for the domain for JaceMan's blog "toacx4".
Next, the ever available "ping" command, to test name resolution.
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=92ms TTL=244
Reply from 64.233.179.121: bytes=32 time=92ms TTL=244
Reply from 64.233.179.121: bytes=32 time=94ms TTL=244
Reply from 64.233.179.121: bytes=32 time=92ms TTL=244
Ping statistics for 64.233.179.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 94ms, Average = 92ms
C:\>ping www.martinezumc.org
Pinging ghs.l.google.com [66.249.81.121] with 32 bytes of data:
Reply from 66.249.81.121: bytes=32 time=94ms TTL=244
Reply from 66.249.81.121: bytes=32 time=92ms TTL=244
Reply from 66.249.81.121: bytes=32 time=93ms TTL=244
Reply from 66.249.81.121: bytes=32 time=93ms TTL=244
Ping statistics for 66.249.81.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 94ms, Average = 93ms
C:\>ping toacx4.info
Ping request could not find host toacx4.info. Please check the name and try again.
C:\>ping www.toacx4.info
Pinging ghs.l.google.com [66.249.81.121] with 32 bytes of data:
Reply from 66.249.81.121: bytes=32 time=93ms TTL=244
Reply from 66.249.81.121: bytes=32 time=92ms TTL=244
Reply from 66.249.81.121: bytes=32 time=106ms TTL=244
Reply from 66.249.81.121: bytes=32 time=93ms TTL=244
Ping statistics for 66.249.81.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 106ms, Average = 96ms
Finally, we'll load all 4 aliases for each blog.
We see a major difference in functionality here. The first, "martinezumc.org", loads its custom website properly for the root only, but not for "www.martinezumc.org". The second, "toacx4.info", loads the website properly for both the root and "www.toacx4.info".
martinezumc .blogspot .com
http://martinezumc.blogspot.com/, which redirects to http://martinezumc.org/
www .martinezumc .blogspot .com
http://www.martinezumc.blogspot.com/
martinezumc .org
http://martinezumc.org/
www .martinezumc .org
http://www.martinezumc.org/ is a 404 at Blogger
toacx4 .blogspot .com
http://toacx4.blogspot.com/, which redirects to http://www.toacx4.info/
www .toacx4 .blogspot .com
http://www.toacx4.blogspot.com/
toacx4 .info
http://toacx4.info/, which redirects to http://www.toacx4.info/
www .toacx4 .info
http://www.toacx4.info/
So why did I refer to The Silence, here? Because less than a week ago, we were told that .info TLDs cannot be used with Custom Domains.
(Edit 2/9 21:00): In custom domain with 1 & 1 hosting, we see the same situation with Cool Looking Stuff as with Martinez UMC.
- http://cool-looking-stuff.blogspot.com/
- http://www.cool-looking-stuff.blogspot.com/
- http://cool-looking-stuff.com/
- http://www.cool-looking-stuff.com/
- DNS Report for cool-looking-stuff.com
>> Top
3 comments:
I'm having similar problems with my custom domain blog. http://celebritymakeupbag.com will not work but http://www.celebritymakeupbag.com works fine. Obviously, I need it work both ways. I hope Blogger fixes this soon.
Same here.
http://www.exploringblogosphere.com works;
but http://exploringblogosphere.com
doesn't work.
How can I solve this problem?
Thanks!
I'm thirding this, http://window.org.nz works, but http://www.window.org.nz doesn't. Any updates on why this is occuring, or workarounds? Asked my domain name company about it, and they can setup URL redirection, etc but that will cause disruption to my site. They said Google should have set it up correctly to go to both the www and non-www domain names.
Post a Comment