Skip to main content

When Correcting A DNS "CNAME", Maybe Delete Before Adding

Very few registrars allow multiple "CNAME" addresses, for a single DNS host.

When I diagnose DNS address problems, I generally recommend
Add the addresses highlighted in green.
Remove the addresses highlighted in red.
I find that it helps to have the old address visible, while the new address is being composed. This does not always produce the desired result, unfortunately.

Many registrars do not allow multiple "CNAME" addresses, for DNS hosts - and the zone editors reject new address attempts.

When DNS addresses for a Blogger custom domain need to be corrected, I recommend
Add the addresses highlighted in green.
Remove the addresses highlighted in red.
I recommend correction in this order, so the blog owner can view the current (incorrect) addresses, while adding new (correct) addresses. This compensates for various zone editor syntax oddities.

Making corrections in this order - adding correct addresses, then removing incorrect addresses - does not always produce the anticipated results. If the zone editor checks as each individual address change is made, we see the result.


"That name is reserved (already in use)."



Some zone editors check, immediately, when a second "CNAME" is entered, for a given "Host" address. When multiple "CNAME"s are forbidden, and the zone editor checks for multiple "CNAME"s immediately, we have a problem.

Other zone editors check for a correct address complement, when Saving multiple zone editor changes - after all additions and removals are successfully made and verified. These zone editors do not present a challenge - as long as the blog owner removes all incorrect addresses.

When the incorrect addresses are not removed properly, we see the result.

That name is reserved (already in use).

This leads the blog owner to cancel the recommended correction - and we wait, in vain, for the domain to come online.

In a worse case scenario, we can even end up with another case of "Another blog ...".

Right now, though, we can only diagnose the problem, one domain at a time.



Some registrars have zone editors which forbid multiple "CNAME"s for specific addresses - and check, one entry at a time, for mistakes. This may cause a problem, with a #Blogger blog owner making custom domain DNS address corrections, when instructed to "Add addresses highlighted in green.", then "Delete addresses highlighted in red."

Comments

Aaron Johnson said…
That's extremely helpful! And your post is extremely detailed. I'm always careful when using cname records.

Popular posts from this blog

Add A Custom Redirect, If You Change A Post URL

When you rename a blog, the most that you can do, to keep the old URL useful, is to setup a stub post , with a clickable link to the new URL. Yo! The blog is now at xxxxxxx.blogspot.com!! Blogger forbids gateway blogs, and similar blog to blog redirections . When you rename a post, you can setup a custom redirect - and automatically redirect your readers to the post, under its new URL. You should take advantage of this option, if you change a post URL.

Referer Spam Is Annoying - And, It's Persistent

Recently, we've seen a few blog owners who are curious about odd trends in their Stats displays. My numbers seem to go up steadily for a while, then drop. Then, they go up again, for a while, then drop again. Rises and falls in traffic are normal. You'll never have the same number of people, viewing your blog, constantly. During some days and some hours, our readers are going to be elsewhere, and not viewing our blogs.

Jump Break Is Visible Only In An Index Page

Some blog owners are unsure what a Jump Break looks like, when applied to their blogs. Occasionally, in Blogger Help Forum: Get Help with an Issue , we see the confusion. Where's the Jump Break? or I added a Jump Break to several posts, but it never shows up! When asked for a screen print of what they're seeing, they may provide a image of the post, in the Post Editor Preview window - or possibly, the published post, but in post page view.