Don't Ever Blame Blogger, Amongst Your Weblog Down!
Wednesday, April 17, 2013
Edit
Some of my favourite occupation reports, inwards Blogger Help Forum: Get Help alongside an Issue, are near inconsistent weblog online status.
Particularly when I encounter the latter symptom, I know precisely where to start.
The "registrar says" is a frequent indicator of the problem. I'm non naming names, but the initial "G" (and non "Google") is real often involved, inwards this case.
So, I outset alongside a Dig log, for the domain. And 99% of the time, that's all that is needed.
Bogus DNS addresses are a real ordinarily seen diagnosis, inwards so many of these cases. For 99.99% of the blogs, published to a custom domain, at that topographic point is but no effective substitute for the "Asymmetrical DNS" setup, provided long ago.
So you lot telephone phone the registrar - as well as they tell you lot that it has to endure Blogger, because they convey no occupation accessing it. But the registrar is business office of the problem.
The righteous address setup.
The domain beginning uses 4 x "A" addresses, accessed inwards a circular robin sequence. And the published URL uses a unmarried "CNAME", resolved using a complex cite server array. With both domain beginning as well as "www" alias properly addressed, your weblog has much improve run a jeopardy of beingness consistently as well as reliably accessed.
One mayhap righteous address setup.
One Blogger Engineer recommended a modified version of the asymmetrical DNS setup, to endure used past times 1&1 customers. Only fourth dimension volition tell if this setup is reliable. I convey seen several 1&1 customers, this year, suggesting that this is non long term reliable.
Some spurious address setups.
Spurious address setups are unlimited, inwards variety. Here are a random three examples, from recent forum history.
Error when adding domain
https://productforums.google.com/d/topic/blogger/WvW2yZaS-FI/discussion
Blogger appears to endure detecting this setup equally a occupation - as well as throws a bX code, to quest a problem.
Mobile Redirection Failure
https://productforums.google.com/d/topic/blogger/rAJgN8pYdPw/discussion
This weblog is online - as well as visible, using broadband - but no domain beginning redirection, for mobile browsing. "50.63.202.10" is non a Blogger / Google cite server, as well as won't render reliable redirection.
Can't divulge my blog
https://productforums.google.com/d/topic/blogger/ibGqKLWXhO8/discussion
This weblog published - but ownership verification did non render the required instant "CNAME".
The bottom line.
There but is no substitute for righteous DNS addressing, for custom domain publishing. Publishing to a custom domain is non a productive activity, if you cannot follow instructions.
The might to divulge a #Blogger weblog to a non BlogSpot URL has been provided, for almost 10 years. Some weblog owners withal cannot setup the domains properly - as well as rest oblivious, when a occupation arises.
Learn why at that topographic point is i effective DNS address setup, for custom domain publishing.
If you lot desire a reliable custom domain, this is the address choice.
It was fine yesterday. Why is it down, now?and
I encounter the blog, just fine! Why are or as well as thence of my readers complaining?and
I tin access it, using my phone! Why is Blogger down, on my abode computer?and
The registrar tells me everything is OK!Whenever I encounter the latter report, I know precisely where to start.
Particularly when I encounter the latter symptom, I know precisely where to start.
The registrar tells me everything is OK!
The "registrar says" is a frequent indicator of the problem. I'm non naming names, but the initial "G" (and non "Google") is real often involved, inwards this case.
So, I outset alongside a Dig log, for the domain. And 99% of the time, that's all that is needed.
Bogus DNS addresses are a real ordinarily seen diagnosis, inwards so many of these cases. For 99.99% of the blogs, published to a custom domain, at that topographic point is but no effective substitute for the "Asymmetrical DNS" setup, provided long ago.
- Maybe the weblog volition endure upward for you, as well as or as well as thence would endure readers - but others volition endure seeing the "404".
- Maybe it was fine, yesterday - as well as today it is suggesting spam as well as viruses.
- It volition entirely work, for or as well as thence people, or as well as thence of the time. That is the entirely constant.
So you lot telephone phone the registrar - as well as they tell you lot that it has to endure Blogger, because they convey no occupation accessing it. But the registrar is business office of the problem.
The righteous address setup.
mydomain.com. 3600 IN H5N1 216.239.32.21
mydomain.com. 3600 IN H5N1 216.239.34.21
mydomain.com. 3600 IN H5N1 216.239.36.21
mydomain.com. 3600 IN H5N1 216.239.38.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
The domain beginning uses 4 x "A" addresses, accessed inwards a circular robin sequence. And the published URL uses a unmarried "CNAME", resolved using a complex cite server array. With both domain beginning as well as "www" alias properly addressed, your weblog has much improve run a jeopardy of beingness consistently as well as reliably accessed.
One mayhap righteous address setup.
One Blogger Engineer recommended a modified version of the asymmetrical DNS setup, to endure used past times 1&1 customers. Only fourth dimension volition tell if this setup is reliable. I convey seen several 1&1 customers, this year, suggesting that this is non long term reliable.
mydomain.com. 3600 IN H5N1 216.239.32.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
Some spurious address setups.
Spurious address setups are unlimited, inwards variety. Here are a random three examples, from recent forum history.
Error when adding domain
https://productforums.google.com/d/topic/blogger/WvW2yZaS-FI/discussion
When i am trying to adding the domain it shows the error
Whoops, that's an error! (bX-6g9yx1)
socialsfriend.com. 600 IN H5N1 184.168.221.33
www.socialsfriend.com. 3600 IN CNAME socialsfriend.com.
Blogger appears to endure detecting this setup equally a occupation - as well as throws a bX code, to quest a problem.
Mobile Redirection Failure
https://productforums.google.com/d/topic/blogger/rAJgN8pYdPw/discussion
When I am on mobile on google chrome (only browser I tested).
chartlearning.com does non redirect to www.chartlearning.com on mobile.
chartlearning.com. 600 IN H5N1 50.63.202.10
www.chartlearning.com. 3600 IN CNAME ghs.google.com.
This weblog is online - as well as visible, using broadband - but no domain beginning redirection, for mobile browsing. "50.63.202.10" is non a Blogger / Google cite server, as well as won't render reliable redirection.
Can't divulge my blog
https://productforums.google.com/d/topic/blogger/ibGqKLWXhO8/discussion
When I entered the "eac-leadership-consulting.com" domain inwards 3rd-party domain settings, I did non have an error. I did non encounter the two CNAME records.
eac-leadership-consulting.com. 600 IN H5N1 50.63.202.50
www.eac-leadership-consulting.com. 3600 IN CNAME eac-leadership-consulting.com.
This weblog published - but ownership verification did non render the required instant "CNAME".
The bottom line.
There but is no substitute for righteous DNS addressing, for custom domain publishing. Publishing to a custom domain is non a productive activity, if you cannot follow instructions.
The might to divulge a #Blogger weblog to a non BlogSpot URL has been provided, for almost 10 years. Some weblog owners withal cannot setup the domains properly - as well as rest oblivious, when a occupation arises.
Learn why at that topographic point is i effective DNS address setup, for custom domain publishing.
If you lot desire a reliable custom domain, this is the address choice.