What Is The Mysterious Custom Domain Fault 12?
Thursday, August 31, 2017
Edit
Both the historically infamous "Another spider web log ..", together with the currently infamous "Error 12", are business office of the custom domain publishing process.
Similar to the mysterious "bX" codes existence an enhanced version of "We're sorry, but nosotros were unable to consummate your request.", "Error 12" (and variants) is an enhanced version of the monolithic "Another spider web log or Google Site is already using this address.".
"Another blog" (which was mostly seen during role of the Blogger Publishing wizard) is complemented past times the as annoying "Not found" (which is mostly seen later on Publishing is used).
The "Another spider web log ..." / "Not Found" status is non desirable - for a working domain.
The condition, inwards general, appears to survive an unavoidable trial of the flexible Blogger custom domain design. H5N1 Blogger custom domain published spider web log tin survive i host inwards a domain cluster, that tin too include a Tumblr blog, a WordPress blog, whatever issue of 3rd political party hosted websites - together with fifty-fifty an strange characteristic similar a forum.
Blogger custom domain publishing is a powerful feature.
Blogger custom domains tin survive purchased from (almost) whatever registrar - together with tin role DNS provided past times (virtually) whatever DNS host. It's to a greater extent than powerful than competing Internet services. Use of "CNAME" referral, to connect the spider web log together with domain, is innovative, together with smart.
Custom domain publishing does around of the domain processing from your calculator - instead of only from Google. Use of your computer, unfortunately, involves computers together with networks uncontrolled past times Google - together with may Pb to occasional database corruption, together with to "Another blog". Custom domain publishing depends upon DNS - together with DNS is an Internet service controlled past times neither Google or whatever spider web log owner.
"Another blog" together with "Not found" are ii displays, caused past times i problem.
The mysterious "Server Not Found", seen occasionally, is similar to the classic "Another spider web log ..." error.
In many cases, righteous DNS addressing is acquaint - but broken links, inwards the Google database, instruct out the spider web log displayed as “Not found”. "Another blog" is seen past times the spider web log owner, when publishing - together with "Not found" is typically seen past times would survive spider web log readers, together with search engines, later on publishing.
An experienced spider web log possessor would mostly prefer the former, to the latter. The owner, when seeing "Another blog", tin cook the problems - together with therefore prospective readers together with search engines tin stance the blog, without seeing "Not Found".
"Error 12" is the best known, but non the only, "Error".
"Error 12" is the best known "Error" - but non the only one. There seem to genuinely survive several dozen dissimilar variants of "Error 12", which refer to problems amongst the Publishing dashboard wizard. We've seen "Error 32", at least.
32 "Error" codes is nowhere as complex as 36^6 "bX" codes - but it's a start.
An representative of the infamous "Error 12", seen long ago.
Earlier, "domain ownership verification was needed, when publishing to newly setup domains. We have, during the past times year, seen reports of Publishing problems labeled "Error 13", "Error 14", together with "Error 32".
"Error 12", inwards reality, is non an actual mistake status - it is exactly a domain, requiring normal ownership verification. Recently, the "Error 12" label was removed from the "domain ownership verification is needed" display - together with now, nosotros exactly consider the label "Third political party domain settings".
"Error 13", "Error 14", together with "Error 32" seem to too involve domain ownership verification - but amongst slightly dissimilar circumstances. There may too survive around "Error" numbers which involve features other than domain ownership verification. And around "bX" codes are caused past times bogus DNS addressing, encountered during custom domain publishing - similar diverse "Error" codes.
The "Error 12" seen now, amongst verification instructions re written - together with without the "Error 12" label.
Ownership verification has choke both to a greater extent than flexible - together with less necessary.
Domains purchased through Google Domains don't involve ownership verification, when purchased nether the Blogger / Google draw concern human relationship as the spider web log owner. The Google Domains service, originally available only to USA residents, is right away (as of August 2018) available inwards Australia, Brazil, Canada, France, India, Indonesia, Italy, Japan, Mexico, Netherlands, Spain, Thailand, UK, USA, together with Vietnam..
Also, Blogger right away accepts domain ownership verification using options available through Google Webmaster Tools - the latter right away itself known as Search Console. These options offering verification mightiness to spider web log owners who can't role simple "CNAME" referral.
Originally, add-on of a novel "CNAME" was necessary, for each role of Publishing - amongst a novel BlogSpot URL involved. After Blogger tuned the verification process, nosotros noted that the minute "CNAME" is only required for a new, unverified domain - together with non ever that, either.
With the "Error 12" designation retired, the other Publishing "Error" labels reference actual mistake atmospheric condition - together with may offering to a greater extent than diagnostic mightiness than the monolithic "Another blog".
For people fortunate to survive able to role Google Domains, buy together with setup of a non BlogSpot address is slow becoming a projection to a greater extent than doable past times spider web log owners, instead of past times tech experts. And the "Error 12" variants volition brand diagnosis of mutual publishing errors to a greater extent than possible.
When Blogger added domain ownership verification to the custom domain publishing procedure inwards 2012, spider web log owners started seeing the mysterious "Error 12", suggesting that ownership verification was required. We've seen diverse other "Error" codes inwards the past times five years, - around too referencing ownership verification, together with others referencing other publishing problems.
It appears that the diverse "Error" codes are used to position problems encountered inwards the Publishing wizard, similar to how the bX codes are used to position problems inwards Blogger, inwards general.
https://productforums.google.com/d/topic/blogger/3Rb3E08zHKk/discussion
https://productforums.google.com/d/topic/blogger/EBhTkj_gdnY/discussion
Similar to the mysterious "bX" codes existence an enhanced version of "We're sorry, but nosotros were unable to consummate your request.", "Error 12" (and variants) is an enhanced version of the monolithic "Another spider web log or Google Site is already using this address.".
"Another blog" (which was mostly seen during role of the Blogger Publishing wizard) is complemented past times the as annoying "Not found" (which is mostly seen later on Publishing is used).
The "Another spider web log ..." / "Not Found" status is non desirable - for a working domain.
The condition, inwards general, appears to survive an unavoidable trial of the flexible Blogger custom domain design. H5N1 Blogger custom domain published spider web log tin survive i host inwards a domain cluster, that tin too include a Tumblr blog, a WordPress blog, whatever issue of 3rd political party hosted websites - together with fifty-fifty an strange characteristic similar a forum.
Blogger custom domain publishing is a powerful feature.
Blogger custom domains tin survive purchased from (almost) whatever registrar - together with tin role DNS provided past times (virtually) whatever DNS host. It's to a greater extent than powerful than competing Internet services. Use of "CNAME" referral, to connect the spider web log together with domain, is innovative, together with smart.
Custom domain publishing does around of the domain processing from your calculator - instead of only from Google. Use of your computer, unfortunately, involves computers together with networks uncontrolled past times Google - together with may Pb to occasional database corruption, together with to "Another blog". Custom domain publishing depends upon DNS - together with DNS is an Internet service controlled past times neither Google or whatever spider web log owner.
"Another blog" together with "Not found" are ii displays, caused past times i problem.
The mysterious "Server Not Found", seen occasionally, is similar to the classic "Another spider web log ..." error.
In many cases, righteous DNS addressing is acquaint - but broken links, inwards the Google database, instruct out the spider web log displayed as “Not found”. "Another blog" is seen past times the spider web log owner, when publishing - together with "Not found" is typically seen past times would survive spider web log readers, together with search engines, later on publishing.
An experienced spider web log possessor would mostly prefer the former, to the latter. The owner, when seeing "Another blog", tin cook the problems - together with therefore prospective readers together with search engines tin stance the blog, without seeing "Not Found".
"Error 12" is the best known, but non the only, "Error".
"Error 12" is the best known "Error" - but non the only one. There seem to genuinely survive several dozen dissimilar variants of "Error 12", which refer to problems amongst the Publishing dashboard wizard. We've seen "Error 32", at least.
32 "Error" codes is nowhere as complex as 36^6 "bX" codes - but it's a start.
Earlier, "domain ownership verification was needed, when publishing to newly setup domains. We have, during the past times year, seen reports of Publishing problems labeled "Error 13", "Error 14", together with "Error 32".
"Error 12", inwards reality, is non an actual mistake status - it is exactly a domain, requiring normal ownership verification. Recently, the "Error 12" label was removed from the "domain ownership verification is needed" display - together with now, nosotros exactly consider the label "Third political party domain settings".
"Error 13", "Error 14", together with "Error 32" seem to too involve domain ownership verification - but amongst slightly dissimilar circumstances. There may too survive around "Error" numbers which involve features other than domain ownership verification. And around "bX" codes are caused past times bogus DNS addressing, encountered during custom domain publishing - similar diverse "Error" codes.
Ownership verification has choke both to a greater extent than flexible - together with less necessary.
Domains purchased through Google Domains don't involve ownership verification, when purchased nether the Blogger / Google draw concern human relationship as the spider web log owner. The Google Domains service, originally available only to USA residents, is right away (as of August 2018) available inwards Australia, Brazil, Canada, France, India, Indonesia, Italy, Japan, Mexico, Netherlands, Spain, Thailand, UK, USA, together with Vietnam..
Also, Blogger right away accepts domain ownership verification using options available through Google Webmaster Tools - the latter right away itself known as Search Console. These options offering verification mightiness to spider web log owners who can't role simple "CNAME" referral.
Originally, add-on of a novel "CNAME" was necessary, for each role of Publishing - amongst a novel BlogSpot URL involved. After Blogger tuned the verification process, nosotros noted that the minute "CNAME" is only required for a new, unverified domain - together with non ever that, either.
With the "Error 12" designation retired, the other Publishing "Error" labels reference actual mistake atmospheric condition - together with may offering to a greater extent than diagnostic mightiness than the monolithic "Another blog".
For people fortunate to survive able to role Google Domains, buy together with setup of a non BlogSpot address is slow becoming a projection to a greater extent than doable past times spider web log owners, instead of past times tech experts. And the "Error 12" variants volition brand diagnosis of mutual publishing errors to a greater extent than possible.
When Blogger added domain ownership verification to the custom domain publishing procedure inwards 2012, spider web log owners started seeing the mysterious "Error 12", suggesting that ownership verification was required. We've seen diverse other "Error" codes inwards the past times five years, - around too referencing ownership verification, together with others referencing other publishing problems.
It appears that the diverse "Error" codes are used to position problems encountered inwards the Publishing wizard, similar to how the bX codes are used to position problems inwards Blogger, inwards general.
https://productforums.google.com/d/topic/blogger/3Rb3E08zHKk/discussion
https://productforums.google.com/d/topic/blogger/EBhTkj_gdnY/discussion