This blog is "blogging.nitecruzr.net".
If I wanted to dress it up a bit, I might tell you it's "Blogging.Nitecruzr.Net". Either URL should work, equally well.
That's not the case with all blogs, today. Here's an example - "mydomain.com". A normal DNS configuration, per an excerpted Dig log.
The HTTP traces are rather unique.
First, look at "mydomain.blogspot.com", in 2 variations. Look carefully at the URLs - the upper case letters aren't decorative.
Apparently published to "www.MyDomain.com", from seeing the feed URLs. There's a variation of this result. See if you can spot the difference.
The first trace is what you see after transition period has expired, and the blog is explicitly published to the custom domain URL. The second trace is what you see during the transition period, with the blog published to the domain URL (see the feed URL?), but without a "301 Moved Permanently" redirect in place.
OK, so far. How about "www.mydomain.com"?
And here's what you get, when accessing the blog. Look closely at the URL, in the address window. "mydomain.blogspot.com" --> "www.mydomain.com", which can't be found, since the blog was published to "www.MyDomain.com".
D'ohh.
Maybe publishing your blog, using mixed case in the name, isn't a good idea.
This looks like a case of case observation / case preservation gone wrong.
In this case, my advice would be given as
If you do see the latter error, recycle the domain settings in Google Apps, persistently. Then re publish to the "www" alias again.
If I wanted to dress it up a bit, I might tell you it's "Blogging.Nitecruzr.Net". Either URL should work, equally well.
That's not the case with all blogs, today. Here's an example - "mydomain.com". A normal DNS configuration, per an excerpted Dig log.
MyDomain.com. 3600 IN A 216.239.32.21
MyDomain.com. 3600 IN A 216.239.34.21
MyDomain.com. 3600 IN A 216.239.36.21
MyDomain.com. 3600 IN A 216.239.38.21
www.MyDomain.com. 3600 IN CNAME ghs.google.com.
---
ghs.google.com. 32316 IN CNAME ghs.l.google.com.
ghs.l.google.com. 300 IN A 74.125.43.121
The HTTP traces are rather unique.
First, look at "mydomain.blogspot.com", in 2 variations. Look carefully at the URLs - the upper case letters aren't decorative.
GET / HTTP/1.1
Host: mydomain.blogspot.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Connection: close
• Finding host IP address...
• Host IP address = 209.85.133.191
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·301·Moved·Permanently(CR)(LF)
Location:·http://www.MyDomain.com/(CR)(LF)
Sending request:
GET / HTTP/1.1
Host: www.MyDomain.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Connection: close
• Finding host IP address...
• Host IP address = 209.85.171.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)
...
<link·rel="alternate"·type="application/atom+xml"·title="My·Blog·-·Atom"
·href="http://www.MyDomain.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="My·Blog·-·RSS"
·href="http://www.MyDomain.com/feeds/posts/default?alt=rss"·/>(LF)
Apparently published to "www.MyDomain.com", from seeing the feed URLs. There's a variation of this result. See if you can spot the difference.
GET / HTTP/1.1
Host: mydomain.blogspot.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Connection: close
• Finding host IP address...
• Host IP address = 74.125.19.191
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)
...
<link·rel="alternate"·type="application/atom+xml"·title="My·Blog·-·Atom"
·href="http://www.MyDomain.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="My·Blog·-·RSS"
·href="http://www.MyDomain.com/feeds/posts/default?alt=rss"·/>(LF)
The first trace is what you see after transition period has expired, and the blog is explicitly published to the custom domain URL. The second trace is what you see during the transition period, with the blog published to the domain URL (see the feed URL?), but without a "301 Moved Permanently" redirect in place.
OK, so far. How about "www.mydomain.com"?
Sending request:
GET / HTTP/1.1
Host: www.mydomain.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Connection: close
• Finding host IP address...
• Host IP address = 209.85.171.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·404·Not·Found(CR)(LF)
And here's what you get, when accessing the blog. Look closely at the URL, in the address window. "mydomain.blogspot.com" --> "www.mydomain.com", which can't be found, since the blog was published to "www.MyDomain.com".
D'ohh.
Maybe publishing your blog, using mixed case in the name, isn't a good idea.
This looks like a case of case observation / case preservation gone wrong.
In this case, my advice would be given as
Publish the blog back to BlogSpot, then re publish it to "www.mydomain.com".And hope like heck to not see
http://blogging.nitecruzr.net/2007/11/custom-domain-publishing-and-404-error.html
Another blog is already hosted at this address.
If you do see the latter error, recycle the domain settings in Google Apps, persistently. Then re publish to the "www" alias again.
Comments
Thank you so much for your help. I agree with Sree that Blogger needs to advise people to not put caps in their custom URLs!