I added the recommended A and CNAME entries (although I'm not sure
where I put the "1800" and "3600" in GoDaddy's totalDNS control page).
I tried the Magic Reset form on Friday, but no luck yet.
Could the problem stem from leaving on the "locked" option in
Godaddy's administrative console? Does it need to be unlocked to map
blogger to the custom domain? I think I tried that the last time I
had this problem a couple years ago, ended up with some robot parking
spam on my domain.
> I added the recommended A and CNAME entries (although I'm not sure
> where I put the "1800" and "3600" in GoDaddy's totalDNS control page).
> I tried the Magic Reset form on Friday, but no luck yet.
> Could the problem stem from leaving on the "locked" option in
> Godaddy's administrative console? Does it need to be unlocked to map
> blogger to the custom domain? I think I tried that the last time I
> had this problem a couple years ago, ended up with some robot parking
> spam on my domain.
> Thanks!
> -James
Hi James,
The "1800" and "3600" are "TTL" aka "Time To Live", and represents the
lifetime of a cached DNS entry in seconds. What you have looks good.
jamesbovay.net. 3600 IN A 64.233.179.121
jamesbovay.net. 3600 IN A 72.14.207.121
www.jamesbovay.net. 3600 IN CNAME ghs.google.com.
The "locked" option is a DNS Hosting setting, that keeps another
hosting service from aggressively grabbing your domain. That setting
"Locked" is on every domain that I work with too. I don't think it
has anything to do with the problem.
I'll put your domain in a special queue for Gatsby now.
> > I added the recommended A and CNAME entries (although I'm not sure
> > where I put the "1800" and "3600" in GoDaddy's totalDNS control page).
> > I tried the Magic Reset form on Friday, but no luck yet.
> > Could the problem stem from leaving on the "locked" option in
> > Godaddy's administrative console? Does it need to be unlocked to map
> > blogger to the custom domain? I think I tried that the last time I
> > had this problem a couple years ago, ended up with some robot parking
> > spam on my domain.
> > Thanks!
> > -James
> Hi James,
> The "1800" and "3600" are "TTL" aka "Time To Live", and represents the
> lifetime of a cached DNS entry in seconds. What you have looks good.
> jamesbovay.net. 3600 IN A 64.233.179.121
> jamesbovay.net. 3600 IN A 72.14.207.121www.jamesbovay.net. 3600 IN CNAME ghs.google.com.
> The "locked" option is a DNS Hosting setting, that keeps another
> hosting service from aggressively grabbing your domain. That setting
> "Locked" is on every domain that I work with too. I don't think it
> has anything to do with the problem.
> I'll put your domain in a special queue for Gatsby now.
> > > I added the recommended A and CNAME entries (although I'm not sure
> > > where I put the "1800" and "3600" in GoDaddy's totalDNS control page).
> > > I tried the Magic Reset form on Friday, but no luck yet.
> > > Could the problem stem from leaving on the "locked" option in
> > > Godaddy's administrative console? Does it need to be unlocked to map
> > > blogger to the custom domain? I think I tried that the last time I
> > > had this problem a couple years ago, ended up with some robot parking
> > > spam on my domain.
> > > Thanks!
> > > -James
> > Hi James,
> > The "1800" and "3600" are "TTL" aka "Time To Live", and represents the
> > lifetime of a cached DNS entry in seconds. What you have looks good.
> >jamesbovay.net. 3600 IN A 64.233.179.121
> >jamesbovay.net. 3600 IN A 72.14.207.121www.jamesbovay.net. 3600 IN CNAME ghs.google.com.
> > The "locked" option is a DNS Hosting setting, that keeps another
> > hosting service from aggressively grabbing your domain. That setting
> > "Locked" is on every domain that I work with too. I don't think it
> > has anything to do with the problem.
> > I'll put your domain in a special queue for Gatsby now.
Thx again Chuck. You're a real pal Chuck. (sorry, Peppermint Patty
impressions are tough with no verbal or visual cues)
I'm not sure what you mean by "recycling"?
The DNS was set right before my first post. Currently my blog is
publishing at the .blogspot subdomain (jamesbovay.blogspot.com). I've
been trying about once a day to set advanced setting to: www.jamesbovay.net,
but still get the "another blog is hosted" message.
Strangely, setting it to just "jamesbovay.net" works, but I still get
the custom domain error when I try to redirect to www. I'd leave it
there but it looks kind of naked to me.
> Thx again Chuck. You're a real pal Chuck. (sorry, Peppermint Patty
> impressions are tough with no verbal or visual cues)
> I'm not sure what you mean by "recycling"?
> The DNS was set right before my first post. Currently my blog is
> publishing at the .blogspot subdomain (jamesbovay.blogspot.com). I've
> been trying about once a day to set advanced setting to:www.jamesbovay.net,
> but still get the "another blog is hosted" message.
> Strangely, setting it to just "jamesbovay.net" works, but I still get
> the custom domain error when I try to redirect to www. I'd leave it
> there but it looks kind of naked to me.
Recycling the publishing is publishing back to BlogSpot, then re
publishing to the custom domain URL.
Let me work this one up properly. I will be redundant, apologies for
doing so.
Your primary symptom is
"Server Not Found
Error 404"
for both "jamesbovay.net" and "www.jamesbovay.net".
An HTTP Access Log shows:
###
Sending request:
GET / HTTP/1.1
Host: jamesbovay.net
• Finding host IP address...
• Host IP address = 72.14.207.121
.
Receiving Header:
HTTP/1.1·404·Not·Found(CR)(LF)
In other words, the primary URL appears to be "jamesbovay.net".
Your DNS configuration is still:
jamesbovay.net. 3600 IN A 64.233.179.121
jamesbovay.net. 3600 IN A 72.14.207.121
www.jamesbovay.net. 3600 IN CNAME ghs.google.com.
The BlogSpot URL, "jamesbovay.blogspot.com", appears to be published
to "jamesbovay.blogspot.com".
Please try re publishing to "www.jamesbovay.net", and let me know when
you're done.
> > Thx again Chuck. You're a real pal Chuck. (sorry, Peppermint Patty
> > impressions are tough with no verbal or visual cues)
> > I'm not sure what you mean by "recycling"?
> > The DNS was set right before my first post. Currently my blog is
> > publishing at the .blogspot subdomain (jamesbovay.blogspot.com). I've
> > been trying about once a day to set advanced setting to:www.jamesbovay.net,
> > but still get the "another blog is hosted" message.
> > Strangely, setting it to just "jamesbovay.net" works, but I still get
> > the custom domain error when I try to redirect to www. I'd leave it
> > there but it looks kind of naked to me.
> Recycling the publishing is publishing back to BlogSpot, then re
> publishing to the custom domain URL.
> Let me work this one up properly. I will be redundant, apologies for
> doing so.
> Your primary symptom is
> "Server Not Found
> Error 404"
> for both "jamesbovay.net" and "www.jamesbovay.net".
> An HTTP Access Log shows:
> ###
> Sending request:
> GET / HTTP/1.1
> Host:jamesbovay.net
> • Finding host IP address...
> • Host IP address = 72.14.207.121
> .
> Receiving Header:
> HTTP/1.1·404·Not·Found(CR)(LF)
> In other words, the primary URL appears to be "jamesbovay.net".
> Your DNS configuration is still:jamesbovay.net. 3600 IN A 64.233.179.121jamesbovay.net. 3600 IN A 72.14.207.121www.jamesbovay.net. 3600 IN CNAME ghs.google.com.
> The BlogSpot URL, "jamesbovay.blogspot.com", appears to be published
> to "jamesbovay.blogspot.com".
> Please try re publishing to "www.jamesbovay.net", and let me know when
> you're done.
> fill in the captcha and: "another blog is published at this address"
> On Nov 18, 9:23 pm, nitecruzr wrote:
> > On Nov 18, 5:39 pm, jameslbovay wrote:
> > > Thx again Chuck. You're a real pal Chuck. (sorry, Peppermint Patty
> > > impressions are tough with no verbal or visual cues)
> > > I'm not sure what you mean by "recycling"?
> > > The DNS was set right before my first post. Currently my blog is
> > > publishing at the .blogspot subdomain (jamesbovay.blogspot.com). I've
> > > been trying about once a day to set advanced setting to:www.jamesbovay.net,
> > > but still get the "another blog is hosted" message.
> > > Strangely, setting it to just "jamesbovay.net" works, but I still get
> > > the custom domain error when I try to redirect to www. I'd leave it
> > > there but it looks kind of naked to me.
> > Recycling the publishing is publishing back to BlogSpot, then re
> > publishing to the custom domain URL.
> > Let me work this one up properly. I will be redundant, apologies for
> > doing so.
> > Your primary symptom is
> > "Server Not Found
> > Error 404"
> > for both "jamesbovay.net" and "www.jamesbovay.net".
> > In other words, the primary URL appears to be "jamesbovay.net".
> > Your DNS configuration is still:jamesbovay.net. 3600 IN A 64.233.179.121jamesbovay.net. 3600 IN A 72.14.207.121www.jamesbovay.net. 3600 IN CNAME ghs.google.com.
> > The BlogSpot URL, "jamesbovay.blogspot.com", appears to be published
> > to "jamesbovay.blogspot.com".
> > Please try re publishing to "www.jamesbovay.net", and let me know when
> > you're done.
