This weekend, as the custom domain problems initially observed June 16 continue to be reported, we see now a new symptom. Observed by the administrator of an affected blog, in the Settings - Publishing wizard, will be the warning
In several cases, this is reportedly observed for blogs with righteous DNS addresses.
Why?
Here we have one example, "wakworld.com".
First, we see an extracted Dig log.
Next, an excerpted HTTP trace.
All in all, a normal diagnosis for a blog published to "www.wakworld.com".
Yet, as stated by the owner of the blog,
(Update 6/22 16:00): It appears that this symptom is related to the Custom Domain Redirect Problem of last week.
(Update 6/22): Recent discoveries suggest that this message may be yet another embodiment of the well known symptom "Another blog is already hosted at this address".
>> Top
The DNS record for your domain is not set up correctly yet. If you just purchased this domain the set up process may take up to a day.
In several cases, this is reportedly observed for blogs with righteous DNS addresses.
Why?
Here we have one example, "wakworld.com".
First, we see an extracted Dig log.
wakworld.com. 3600 IN A 216.239.32.21
wakworld.com. 3600 IN A 216.239.34.21
wakworld.com. 3600 IN A 216.239.36.21
wakworld.com. 3600 IN A 216.239.38.21
www.wakworld.com. 3600 IN CNAME ghs.google.com.
Next, an excerpted HTTP trace.
Sending request:
GET / HTTP/1.1
Host: wakworld.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11
Connection: close
• Finding host IP address...
• Host IP address = 216.239.38.21
• 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://www.wakworld.com/(CR)(LF)
Sending request:
Sending request:
GET / HTTP/1.1
Host: www.wakworld.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11
Connection: close
• Finding host IP address...
• Host IP address = 74.125.47.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="Will·and·Kate's·World·-·Atom"·href="http://www.wakworld.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="Will·and·Kate's·World·-·RSS"·href="http://www.wakworld.com/feeds/posts/default?alt=rss"·/>(LF)
All in all, a normal diagnosis for a blog published to "www.wakworld.com".
Yet, as stated by the owner of the blog,
I have disabled all google apps, and am pretty sure my DNS is righteous but still the error notice persist.The DNS record for your domain is not set up correctly yet.
(Update 6/22 16:00): It appears that this symptom is related to the Custom Domain Redirect Problem of last week.
(Update 6/22): Recent discoveries suggest that this message may be yet another embodiment of the well known symptom "Another blog is already hosted at this address".
- As necessary, correct your DNS addresses.
- Recycle the publishing of the blog address.
- Recycle the domain settings, in Google Apps.
>> Top
Comments
Fingers crossed that the bug has been fixed!
(Nitecruzr, you've responded earlier on my Blogger Help thread discussing this.)