Sometimes, after setting up a blog, publishing it to a custom domain, and dealing with the "404 Not Found" and the "Another blog ..." / "naked domain" errors, we get a working custom domain. And just as knowing what diagnostics we do not want to see, it's good to know what we do want to see.
Here, for instance, we have a blog published to "blog.mydomain.com", which is a virtual host in the domain "mydomain.com".
First, an excerpted Dig log.
Next, an excerpted HTTP trace.
Congratulations, this one is good to go.
>> Top
Here, for instance, we have a blog published to "blog.mydomain.com", which is a virtual host in the domain "mydomain.com".
First, an excerpted Dig log.
blog.mydomain.com. 3600 IN CNAME ghs.google.com.
www.blog.mydomain.com. 3600 IN CNAME ghs.google.com.
Next, an excerpted HTTP trace.
Sending request:
GET / HTTP/1.1
Host: www.blog.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·302·Moved·Temporarily(CR)(LF)
Location:·http://blog.mydomain.com/(CR)(LF)
Sending request:
GET / HTTP/1.1
Host: blog.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"·href="http://blog.mydomain.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·href="http://blog.mydomain.com/feeds/posts/default?alt=rss"·/>(LF)
Congratulations, this one is good to go.
>> Top
Comments