Don't Ever Blame Blogger, Amongst Your Weblog Down!
Tuesday, December 16, 2014
Edit
Some of my favourite work reports, inward Blogger Help Forum: Get Help alongside an Issue, are almost inconsistent weblog online status.
Particularly when I run across the latter symptom, I know just 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 oft involved, inward this case.
So, I starting fourth dimension alongside a Dig log, for the domain. And 99% of the time, that's all that is needed.
Bogus DNS addresses are a real usually seen diagnosis, inward so many of these cases. For 99.99% of the blogs, published to a custom domain, at that topographic point is just no effective substitute for the "Asymmetrical DNS" setup, provided long ago.
So yous telephone phone the registrar - too they tell yous that it has to hold upwards Blogger, because they accept no work accessing it. But the registrar is business office of the problem.
The righteous address setup.
The domain rootage uses 4 x "A" addresses, accessed inward a circular robin sequence. And the published URL uses a unmarried "CNAME", resolved using a complex refer server array. With both domain rootage too "www" alias properly addressed, your weblog has much improve peril of existence consistently too reliably accessed.
One perchance righteous address setup.
One Blogger Engineer recommended a modified version of the asymmetrical DNS setup, to hold upwards used past times 1&1 customers. Only fourth dimension volition tell if this setup is reliable. I accept seen several 1&1 customers, this year, suggesting that this is non long term reliable.
Some spurious address setups.
Spurious address setups are unlimited, inward 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 hold upwards detecting this setup every bit a work - too throws a bX code, to signal a problem.
Mobile Redirection Failure
https://productforums.google.com/d/topic/blogger/rAJgN8pYdPw/discussion
This weblog is online - too visible, using broadband - but no domain rootage redirection, for mobile browsing. "50.63.202.10" is non a Blogger / Google refer server, too 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 minute "CNAME".
The bottom line.
There just 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 mightiness to divulge a #Blogger weblog to a non BlogSpot URL has been provided, for almost 10 years. Some weblog owners yet cannot setup the domains properly - too stay oblivious, when a work arises.
Learn why at that topographic point is 1 effective DNS address setup, for custom domain publishing.
If yous desire a reliable custom domain, this is the address choice.
It was fine yesterday. Why is it down, now?and
I run across the blog, just fine! Why are around of my readers complaining?and
I tin forcefulness out access it, using my phone! Why is Blogger down, on my habitation computer?and
The registrar tells me everything is OK!Whenever I run across the latter report, I know just where to start.
Particularly when I run across the latter symptom, I know just 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 oft involved, inward this case.
So, I starting fourth dimension alongside a Dig log, for the domain. And 99% of the time, that's all that is needed.
Bogus DNS addresses are a real usually seen diagnosis, inward so many of these cases. For 99.99% of the blogs, published to a custom domain, at that topographic point is just no effective substitute for the "Asymmetrical DNS" setup, provided long ago.
- Maybe the weblog volition hold upwards up for you, too around would hold upwards readers - but others volition hold upwards seeing the "404".
- Maybe it was fine, yesterday - too today it is suggesting spam too viruses.
- It volition alone work, for around people, around of the time. That is the alone constant.
So yous telephone phone the registrar - too they tell yous that it has to hold upwards Blogger, because they accept no work accessing it. But the registrar is business office of the problem.
The righteous address setup.
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.34.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.36.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.38.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
The domain rootage uses 4 x "A" addresses, accessed inward a circular robin sequence. And the published URL uses a unmarried "CNAME", resolved using a complex refer server array. With both domain rootage too "www" alias properly addressed, your weblog has much improve peril of existence consistently too reliably accessed.
One perchance righteous address setup.
One Blogger Engineer recommended a modified version of the asymmetrical DNS setup, to hold upwards used past times 1&1 customers. Only fourth dimension volition tell if this setup is reliable. I accept seen several 1&1 customers, this year, suggesting that this is non long term reliable.
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
Some spurious address setups.
Spurious address setups are unlimited, inward 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 Influenza A virus subtype H5N1 184.168.221.33
www.socialsfriend.com. 3600 IN CNAME socialsfriend.com.
Blogger appears to hold upwards detecting this setup every bit a work - too throws a bX code, to signal 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 Influenza A virus subtype H5N1 50.63.202.10
www.chartlearning.com. 3600 IN CNAME ghs.google.com.
This weblog is online - too visible, using broadband - but no domain rootage redirection, for mobile browsing. "50.63.202.10" is non a Blogger / Google refer server, too 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 inward 3rd-party domain settings, I did non have an error. I did non run across the ii CNAME records.
eac-leadership-consulting.com. 600 IN Influenza A virus subtype 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 minute "CNAME".
The bottom line.
There just 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 mightiness to divulge a #Blogger weblog to a non BlogSpot URL has been provided, for almost 10 years. Some weblog owners yet cannot setup the domains properly - too stay oblivious, when a work arises.
Learn why at that topographic point is 1 effective DNS address setup, for custom domain publishing.
If yous desire a reliable custom domain, this is the address choice.