Skip to main content

Google Domains Support, And "code CONFLICT"

As domains registered by Google Domains become more popular, we're seeing more problem reports, referencing broken domains, in Blogger Help Forum: Get Help with an Issue.

If I try to load my blog, I get the error
An error occurred (code CONFLICT). Please try again.
I bought my domain through Google Domains.

We're enjoying the personal support options provided by Google Domains - online chat, email, and voice chat.

It appears that Google Domains now provides a domain reset procedure, that may resolve the "code CONFLICT" error, on a domain by domain basis.

When contacted, and the "code CONFLICT" error is mentioned, Google Domains provides a reset script, that resembles the legendary Google Apps Domain Reset procedure.
  1. Clear Google Domains Synthetic records.
  2. Re publish the blog, to the domain.
  3. Re create the Domain DNS addresses.
From your Google Domains dashboard, click on "My domains" (if necessary). Looking at the menu entry for the broken domain, select the icon in the "DNS" column.

You'll start with the "Configure DNS" page. The "Synthetic records" and "Custom resource records" sections of "Configure DNS" will be used, in this task.

Clear Google Domains Synthetic records.

Using the "Synthetic records" wizard in the Google Domains dashboard, find and delete the "Blogger" entry.

Re publish the blog, to the domain.

Using the "Publishing" wizard in the Blogger dashboard, re publish the blog, to the domain.
  • If the blog is currently published to the domain, click on the "X" and publish back to BlogSpot.
  • Publish the blog to the "www" host of the domain, using the Publishing link "Setup a Google Domains URL for your blog".
  • Redirect the domain root to the "www" alias.

Re create the Domain DNS addresses.

As above, use the "Synthetic records" wizard in the Google Domains dashboard, and delete the "Blogger" entry. Then, use the "Custom resource records" wizard, and add the standard 4 x "A" + "CNAME" DNS address complement. The "CNAME", as recreated, should point to "", not to "".

The script ends with the valuable advice to wait while the DNS changes propagate.
please note that any DNS update can take up to 24 to 48 hours to propagate throughout the internet.
If you are patient and wait, you'll have a better chance of the domain propagating, without recreating the "code CONFLICT" aka "Another blog ..." condition.


Thanks! I was able to fix my new domain with your instructions.
You are the man! Thanks for the help with my domain problem you can see it now works... Thank you
Extremely helpful. Thank you!
Rainy Days Babe said…
Okay I am really trying here & maybe I'm just exhausted or frustrated or completely technologically challenged, but where is the freaking DNS page/button whatever??
Chuck Croll said…
Hey Babe,

The freaking DNS Page/button is on the Google Domains "My domains" menu page, in the entry for the domain.
Jacob Oakes said…
Thank you so much! This was very helpful.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: