Troubleshooting Your Custom Domain Problems

Of the many accessories in addition to features inwards Blogger, Custom Domain Publishing is perchance the most problematic.

Looking at the Labels index inwards this blog, I encounter the Custom Domains label on 363 posts (as of 2015/06/15) - which makes it 1 of the most heavily labeled unmarried topics here. There are several challenges alongside diagnosing in addition to resolving a custom domain problem.

• It has various unlike causes.
• It leads to many unlike symptoms, which tin laissez passer the sack easily last confused for other problems.
• Its symptoms tin laissez passer the sack last chronic or intermittent- in addition to may last immediate, or may accept months to exhibit themselves.
• It may require resolution past times whatever weblog guest, past times the weblog owner, past times Blogger Support, in addition to / or past times a 3rd political party such equally the domain registrar.

---

As y'all read this article, click on or thence of the many links inwards the text, in addition to read the linked articles.

Please intend of this article equally the origin chapter inwards a really large mass - right now, a mass alongside 363 chapters.

---

How To Use This Guide

• Always start properly, alongside properly setup DNS addresses.
• Verify DNS addresses, using Dig. If whatever dubiety nearly Dig results, compare logs from multiple Dig utilities, including a Dig against the authoritative domain server. Possibly 90% of all custom domain problems are caused, straight or indirectly, past times spurious DNS addresses.
  
• If exam of multiple Dig logs shows properly setup DNS addresses, human face at HTTP traces against the BlogSpot in addition to domain URLs.
  
• If neither Dig nor HTTP traces furnish a definitive diagnosis, consider that y'all receive got internal database corruption.
• As y'all diagnose your DNS setup, only human face at "A" in addition to "CNAME" records.
• As y'all diagnose in addition to / or laid upwards the problem, do non delete the Google Apps administrative desktop account.

These are the known custom domain publishing diagnoses. Here's a brief, 1 line summary of the problems, which are discussed, inwards or thence detail, further below. Click on whatever one, if it looks promising, to saltation to the exceptional discussion.

• Domain Purchase Unsuccessful
• Only Name Registration Purchased, No DNS Hosting
• Domain Addresses Not Defined
• Domain Ownership Not Verified
• Non Google DNS server Part Of Configuration
• Domain Addresses Not Properly Chosen
• Domain Previously Registered, And Used In Blogger
• Domain Registration Expired
• Blog Published To Domain, Using Mixed Case URL
• Blog Published To Domain Root, With Asymmetrical DNS
• Domain Redirected To Google Ad Services, Sites, or Start Page URL
• Domain Published, Partially
• Internal Blogger Database Corruption
• The Blog And Domain Are In Transition
• All Issues May Not Be Discussed Here

Domain Purchase Unsuccessful

• The domain volition non last setup. The weblog may, or may not, last published to the domain.
• This volition follow purpose of "Buy a domain".
• The primary symptoms volition vary. We encounter both "404 Not Found", in addition to "Another weblog is already hosted at this address", fairly mutual for this problem.
• This volition last an number for newly purchased domains.
• It volition last diagnosed past times purpose of the WhoIs log showing "xxxxxxx.xxx appears to last available", in addition to verified past times examination of the Google Checkout logs, in addition to banking concern employment concern human relationship ledger entries.
• The weblog possessor to a greater extent than oft than non has to right a employment alongside his banking concern account, thence repeat the purchase of the domain.

Only Name Registration Purchased, No DNS Hosting

• The domain volition non last setup, nor the weblog published to the domain.
• This volition follow domain registration, purchased from a 3rd political party registrar.
• The primary symptom volition last the query "What are the DNS servers for Google?", "I demand 2 IP addresses for my domain!", or "I tin laissez passer the sack exactly alter NameServer1, NameServer2 inwards my domain setup!".
• This volition last an number for newly purchased domains.
• It volition last diagnosed past times the stated symptom, alongside the blogger confirming the diagnosis past times checking the registrar's invoice to encounter what services were paid for.
• The blogger volition receive got to adapt for DNS hosting - gratis or paid - but choose the right DNS hosting service. Influenza A virus subtype H5N1 gratis third political party DNS hosting service may last useful, inwards this case.

Domain Addresses Not Defined

• The weblog volition non last successfully published to the domain.
• This volition follow domain registration using "Buy a domain".
• The primary symptom volition last "Another weblog is already hosted at this address", inwards the Settings - Basic - Publishing display.
• This volition occur for novel custom domains.
• It volition last diagnosed using an excerpted Dig log, for both domain URLs.
• Here, the blogger volition last advised to contact Google Apps Support, for whatever domain buy issues.

Domain Ownership Not Verified

• The weblog volition non last successfully published to the domain.
• The primary symptom volition last an "Error 12" or variant (we receive got observed "Error 12", "Error 13", "Error 14", in addition to "Error 32", inwards reported diverse forum topics), when using the the Settings - Basic - Publishing wizard.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain".
• This volition occur for novel custom domains - equally good equally for mature domain beingness re published.
• This volition last diagnosed using an excerpted Dig log, for both domain URLs. Base DNS addresses should also last verified, to ensure addresses are properly setup.
• The weblog possessor volition last advised to add together or verify presence of the proper domain ownership verification "CNAME". This may involve adding an updated "CNAME", in addition to / or carefully examining the format of the "CNAME", equally entered inwards the "Zone Edit" registrar display. Some weblog owners may demand to purpose a gratis third political party DNS hosting service, to allow for registrars who cannot back upwards the necessary "CNAME".

Non Google DNS server Part Of Configuration

• The weblog may, or may not, last successfully published to the domain.
• This volition follow domain registration, purchased from a 3rd political party registrar.
• The primary symptom may last "Another weblog is already hosted at this address" (for novel custom domains, inwards the Settings - Basic - Publishing display), or conversely "404 Not Found" (for long existing custom domains, when viewing the blog). The symptoms volition last observed intermittently, when the non Google server is referenced.
• Possible secondary symptoms:
  • Blog feeds, intermittently non redirected from the native BlogSpot URL.
  • Commenting problems.
• It volition last diagnosed using an excerpted Dig log, for the domain root.
• It is typically resolved past times a iv pace process. For best results, follow this physical care for religiously.
  1. Publish the weblog dorsum to BlogSpot.
  2. Correct the DNS addresses.
  3. Wait for the DNS latency flow to expire. This is important. Failure to consider DNS latency may afterward Pb to Internal Database Corruption. This flow volition vary, equally a number of the TTL setting inwards the "A" / "CNAME" referral.
  4. Republish to the domain URL.

Domain Addresses Not Properly Chosen

• The weblog may, or may not, last successfully published to the domain.
• This volition follow domain registration, purchased from a 3rd political party registrar.
• The primary symptom may last "Another weblog is already hosted at this address" (for novel custom domains, inwards the Settings - Basic - Publishing display), or conversely "404 Not Found" (for long existing custom domains, when viewing the blog).
• Possible secondary symptoms:
  • Blog feeds, unreliably redirected from the native BlogSpot URL.
  • Commenting problems.
• It volition last diagnosed using an excerpted Dig log, for both domain URLs.
• It is typically resolved past times a iv pace process. For best results, follow this physical care for religiously.
  1. Publish the weblog dorsum to BlogSpot.
  2. Correct the DNS addresses.
  3. Wait for the DNS latency flow to expire. This is important. Failure to consider DNS latency may afterward Pb to Internal Database Corruption. This flow volition vary, equally a number of the TTL setting inwards the "A" / "CNAME" referral.
  4. Republish to the domain URL.

Domain Previously Registered, And Used In Blogger

• A Blogger weblog was successfully published to the domain, at 1 fourth dimension - past times a unlike person. It is at nowadays non successfully published.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain".
• The primary symptom volition last "Another weblog ...", when attempting to issue / re issue the weblog to the domain.
• It volition last diagnosed using an excerpted Dig log, for the BlogSpot, in addition to both domain, URLs.
• It volition last resolved using the Custom Domain Reset form - in addition to much patience past times the electrical current domain owner.

Domain Registration Expired

• The weblog was successfully published to the domain, at 1 time.
• This may follow domain registration, long agone purchased from a 3rd political party registrar, or using "Buy a domain".
• The primary symptom may last unexpected content, displayed past times the blog. The nature of the unexpected content volition vary.
  1. In most cases, in addition to when the weblog possessor is lucky, the domain volition last dead, or maybe display a page of ads or an "Offsite Warning" interstitial display.
  2. In rare cases, in addition to when the weblog possessor is non lucky, the weblog volition display contents of or thence other blog, or thence other website, or an "Offsite Warning" interstitial display.
• It volition last diagnosed using a WhoIs log, which shows perish in addition to terminal update dates, for the domain.
• There are ii possible resolutions (see ii primary symptoms, above, for possible variants).
  1. With the weblog possessor beingness lucky, it is inwards the command of the registrar. After domain registration is renewed, the employment is resolved past times the iv pace process. For best results, follow this physical care for religiously.
     1. Publish the weblog dorsum to BlogSpot.
     2. If necessary (and possible), contact the registrar, in addition to renew the registration. Then, correct the DNS addresses.
     3. Wait for the DNS latency flow to expire. This is important. Failure to consider DNS latency may afterward Pb to Internal Database Corruption. This flow volition vary, equally a number of the TTL setting inwards the "A" / "CNAME" referral.
     4. Republish to the domain URL.
  2. If the weblog possessor was non lucky, the domain may at nowadays last inwards the manus of an unknown party. This volition last a plain of study for or thence other article.

Blog Published To Domain, Using Mixed Case URL

• The weblog volition last successfully published to the domain, but volition non last visible from either BlogSpot or domain URLs.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain".
• The primary symptom volition last a "404 Not Found", when attempting to sentiment the weblog using either the BlogSpot or domain URLs.
• This will, typically, occur for novel custom domains, straight off after the destination of the 3 Day Transition Period.
• It volition last diagnosed using a RexSwain HTTP Trace set, starting from the BlogSpot URL.
• It is typically resolved past times publishing the weblog dorsum to BlogSpot, thence re publishing to the right URL, using all lower illustration letters.

Blog Published To Domain Root, But Asymmetrical DNS Used

• The weblog volition non last successfully published to the domain.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain" - though "Buy a domain" volition last far to a greater extent than normally seen.
• The primary symptom volition last a "404 Not Found", when attempting to sentiment the weblog using either the BlogSpot or domain URLs - or the alert "Blogs may non last hosted at naked domains." or "Another weblog or Google Site is already using this address.", when trying to publish or re issue the weblog to the domain.
• This will, typically, occur for novel custom domains.
• It volition last diagnosed using a RexSwain HTTP Trace set, starting from the BlogSpot URL, in addition to confirmed alongside a hide impress of the Publishing magician display, taken equally the weblog possessor sees the fault message inwards question.
• It is typically resolved past times publishing to the "www" alias.

Domain Redirected To Google Ad Services, Sites, or Start Page URL

• The weblog volition non last successfully published to the domain.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain".
• The primary symptom volition last "Another weblog is already hosted at this address", inwards the Settings - Basic - Publishing display.
• This volition typically occur for novel custom domains.
• It volition last diagnosed using a RexSwain HTTP Trace, starting from either domain URL.
• It is typically resolved past times deactivating or resetting the Ad Services, Sites, or Start Page service, using Google Apps.

Blog Published Partially, To The Custom Domain URL

• The weblog volition appear successfully published to the domain.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain".
• The primary symptom volition last "404 Not Found", when viewing the weblog using 1 of the domain URLs - in addition to the weblog volition all the same last published to the BlogSpot URL.
• It volition last diagnosed using an excerpted Dig log, for the BlogSpot, in addition to both domain, URLs. If each of the to a higher house diagnoses are eliminated, 1 past times one, in addition to "404 Not Found" is all the same observed, internal database corruption is the exactly remaining possibility.
• It is typically resolved past times re publishing the weblog to the domain. This symptom may mask a Service Redirect, or Internal Database Corruption.
• As y'all diagnose the problem, re issue the weblog to the domain, in addition to / or recycle the domain settings, delight do non delete the Apps desktop account.

Internal Blogger Database Corruption

• The weblog volition non last successfully published to the domain.
• This may follow domain registration, purchased from a 3rd political party registrar, or using "Buy a domain".
• The primary symptom volition last "Another weblog or Google Site ..." / "Key already exists ..." / "code CONFLICT" (or a similar phrasing), inwards the Settings - Basic - Publishing display, when attempting to publish or re issue a weblog to the domain.
• It volition last diagnosed using an excerpted Dig log, for both domain URLs. If the to a higher house diagnoses are all eliminated, 1 past times one, in addition to "Another weblog ..." is all the same observed, database corruption is the exactly remaining possibility.
• It is typically resolved past times recycling the domain settings inwards Google Apps, in addition to / or purpose of the use of their domain dashboard.
• As y'all diagnose the employment in addition to / or recycle the domain settings, delight do non delete the Apps desktop account.

The Blog And Domain Are In Transition

• The domain volition last setup - but volition non redirect. The weblog volition last published to the domain URL.
• This volition follow purpose of "Buy a domain".
• The primary symptom volition last seen exactly past times the possessor (when properly logged inwards to Blogger). When clicking on the "View Blog" dashboard push clit / link, the possessor volition encounter an "In Transition" display.
• This volition last a temporary issue, for newly purchased domains, successful purchased.
• It volition last diagnosed using an excerpted Dig log, for the BlogSpot, in addition to both domain, URLs.
• It volition larn away, when Transition expires, 72 to 96 hours after successful domain buy in addition to registration. The blog, in addition to the domain, volition thence redirect properly.
• While y'all hold off for Transition to expire, pass fourth dimension reading what y'all volition desire to do, when Transition is complete.

All Issues May Not Be Yet Discussed Here
You could, occasionally, receive got a employment which is non diagnosed inwards this Guide - in addition to inwards that case, delight inquire for help, politely, inwards Blogger Help Forum: Something Is Broken.

Before bespeak for help, y'all tin laissez passer the sack assist the helpers if y'all receive got tried or thence affinity diagnostics or maybe or thence differential diagnostics - in addition to if y'all are aware that non all problems may last exclusively caused past times Blogger. And receive got or thence thought how many possibilities exist, for problems.

---

And if it's non likewise late, read Blogger Magic - How To Setup Influenza A virus subtype H5N1 Custom Domain, in addition to Setting Up DNS Addresses For Custom Domains, earlier y'all start.

Share this post