Showing posts with label "Another blog ...". Show all posts
Showing posts with label "Another blog ...". Show all posts

Saturday, December 08, 2012

Google Apps Ends Availability Of Their Free Edition

Last week, Google dropped a bombshell on many small client developers.
Starting on December 6, 2012, Google will no longer offer new accounts for the free edition of Google Apps. Google Apps free edition is sometimes referred to as "Standard Edition."

This announcement will bring changes to Blogger, and to custom domain publishing. Many owners of Blogger blogs published using the Google Custom Domain feature have learned to use various Google Apps wizards, to setup and to maintain their domains.

Monday, November 19, 2012

Using The Google Apps Domain Root Redirect Setting

Recently, Google Apps added a setting to the domain administrator desktop GUI, which controls the redirect of the domain root (aka "naked domain"). We initially observed this setting, as an option in working around the problem of setting the domain root redirect, in the Blogger Publishing "Advanced Settings" wizard. It's also possible that this setting should be used in recycling the domain settings, when faced with the "dreaded "Another blog ..." error.

Use of the Google Apps Domain Redirect setting is not complicated. It starts with setup of the domain administrator account. For any newly purchased domain - as well as for domains purchased directly from a registrar, it's a fairly simple matter to setup a Google Apps domain administrator account - then to set (or reset) the redirect.

Monday, October 01, 2012

Blog Owners Seeing bX-afpmyd When Trying To Un Delete Custom Domain Published Blogs

We're seeing a few reports this week, from blog owners who recently deleted their custom domain published blogs - who now lament their decision - and who are unable to un delete the blogs.
I can't "undelete" my blog, that used to be published as a custom domain URL. I received the following error code: bX-afpmyd.
This problem, like others, appears to have started when custom domain publishing was restored, last week.

Friday, August 17, 2012

The Old "Another blog ..." Problem - The Domain Settings In Google Apps

The use of Google Apps, for resetting the domain settings, frequently requires much repetition - yet seldom produces consistent results. Some blog owners are able to disable a single service to get their domain working, others must recycle the service settings repeatedly - and still others must spend time anxiously recycling one service after another, then looking for more, unnamed services to recycle.

Some blog owners look for shortcuts in the recommended process - such as deleting the Apps account, which simply wastes time. Unfortunately, very few shortcuts, when identified, are consistently effective for other blog owners later. This lack of consistency leads to various comments mentioning lack of useful advice, in the forum discussions.

The Old "Another blog ..." Problem - Will It Ever Be Fixed?

The ability to publish a Blogger blog to a non BlogSpot URL - also known as "Custom Domain Publishing" - has been a Blogger option for over 5 years. We have, similarly, observed the problem which is collectively described as "Another blog ..." for almost that long.

Every week, we see the signs of frustration in Blogger Help Forum: Something Is Broken.
Why does Blogger never fix the "Another blog" problem?
or
Why can I never get a straight answer here, about my inability to make my custom domain work?
Both of these questions ignore the reality - that "Another blog ..." is actually a symptom, with many different causes.

Friday, July 27, 2012

You Cannot Buy A Domain From Blogger

One of the odder examples of naivete, seen occasionally in Blogger Help Forum: How Do I?, involves the custom domain purchase.
How do I buy a domain from Blogger?
or alternately
How do I have Google host my domain?
The immediate answer, properly stated, is simple.
You cannot buy a domain from Blogger. Neither Blogger, nor Google, is a registrar.
The full answer, however, is a bit more complex.

Tuesday, June 19, 2012

Custom Domain Diagnoses - Identify DNS Address Inconsistencies

One of the more intriguing causes of intermittent custom domain problems starts with inconsistent DNS server configuration. Recently, eNom, one of the "partners" in "Buy a domain", has been serving inconsistent DNS configurations, from time to time - including one very blatant episode the afternoon of 6/18/2012, which was reported by several dozen angry blog owners.

Detecting, and diagnosing, the inconsistencies is typically a complicated process.
  1. Identify the domain authority servers, typically using a Who Is lookup.
  2. Dig each domain address (typically "naked domain" and "www" aliases), from each of the identified domain authority servers.
  3. Extract and aggregate each Dig log.
  4. Compare aggregated Dig snippets.
This was not a task for the faint of heart, or tech challenged, blog owner.

Recently, I was given a handy tool which does all of this, in one quick GUI transaction.

Tuesday, June 12, 2012

Research Custom Domain Problems From The Beginning Of The Purchase

Sometimes, researching a problem, with a custom domain published blog, involves a Who Is lookup, to determine key domain details - like DNS server namess, purchase date, registrar name, and others. Starting with the properly spelled domain name is essential, to getting a useful Who Is lookup. In cases where the blog / domain owner can't spell the domain name consistently, you can start even more basically.

To determine the details about a domain purchase, when you have any doubt, ask for a copy of the invoice or receipt. If the transaction was conducted electronically, copy and paste of the key information is most useful. If the transaction involved a paper trail, have the receipt scanned, and a picture posted somewhere that you can view.

Thursday, May 31, 2012

Buying A Custom Domain Requires A Working Bank Issued Credit Card

As Blogger in general, and custom domain publishing in particular, becomes more popular in Asia and Africa, we are seeing more problems with the Blogger / Google domain purchase process. The basic problem, in Blogger Help Forum: Something Is Broken, will be expressed so simply.
My blog is showing an off-site redirect.
You're about to be redirected.

The blog that used to be here is now at http://www.mydomain.com.
Do you wish to be redirected?
What do I do now?

Some time ago, this report would have been diagnosed as spurious DNS addresses - and we would point out the necessities of proper custom domain DNS addressing, when setting up the domain yourself. Nowadays, an increasingly common diagnosis, for this problem, is an unsuccessfully purchased domain, using the Blogger / Google "Buy a domain" or Google Apps purchase process.

Wednesday, May 02, 2012

Custom Domain Publishing And Abandoned Blogs

We've been exploring the issues of Custom Domain Publishing for many years. The problem of custom domain database corruption, also known as
Another blog is already hosted at this address.
is one of the most commonly observed symptoms, with custom domain publishing problems.

The most common cause of the "Another blog ..." symptom is broken database pointers. In the past, the broken pointers have been associated with various Google Apps controlled services.
  • Ad Services.
  • Google Sites.
  • Start Page.
Now that Custom Domain Publishing is a mature feature in Blogger, there's a newly seen trend, in problems reported in Blogger Help Forum: Something Is Broken.
  • Blogger Blogs.

Friday, April 20, 2012

Before Publishing Back To BlogSpot, Get The DNS Addresses Right

One problem, occasionally seen in Blogger Help Forum: Something Is Broken, involves blog owners preparing to re use their custom domain for publishing their website - and who now need to publish their Blogger blog back to BlogSpot.
I need to reuse my domain for my website - but when I try to re publish my blog, I keep seeing
Another blog is already hosted at this address.
How can I get my blog back online?

When we look at the domain, and the DNS addresses, we see the domain pointing to the website, already. And this is where many custom domain publishing problems start.

Saturday, April 07, 2012

Confusion Over Domain Expiration Dates Caused By "Buy a domain" Renewal

We're seeing some reports of panic, from a few Blogger blog owners who recently renewed registration of their "Buy a domain" purchased custom domains, with Google Apps informing them that their domain registration is now renewed - but with a back dated expiry. This appears to be a known Google Apps issue.

Roberto of "robertosblogs.net", in Another Google Stuff-up, shows us the confirmation letter, that he recently received from Google Apps.
This message confirms we have renewed your domain registration for robertosblogs.net with GoDaddy.com . Your credit card has been charged $10 and your domain registration is valid until April 5, 2011 .
Some people, reporting this scenario in Blogger Help Forum: Something Is Broken have been rather panicked, and fearful either that they had just wasted $10 - or that their domain now needs an additional payment (for 2 years?).

Thursday, April 05, 2012

Confusion Over Domains Purchased Directly From The Registrar

Blogger / Google offers the optional ability to publish a Blogger blog to any available non BlogSpot URL, aka "Custom Domain Publishing" - and the process of setting up a custom domain is so simple - when we use the "Buy a domain" wizard. As simple as "Buy a domain" is, it involves details that are unbelievably complex - and too many blog owners, avoiding use of "Buy a domain", find out about these details the hard way.

One important detail about custom domain publishing involves the level of service, as purchased from the registrar. There are three basic levels of service, offered by many registrars.
  1. Name registration, only.
  2. DNS hosting / Name registration.
  3. Content hosting / DNS hosting / Name registration.
Choose the wrong service level, and you'll waste either time - or money. And, we all know that "time is money".

Sunday, January 01, 2012

Choose Your Registrar, When Buying A Domain

When you purchase a domain - either as part of the "Buy a domain" wizard, or when you purchase directly from a registrar - you are free to use any registrar that you wish, for the purchase. The "Buy a domain" wizard (which should be your preferred method of purchase) lets you use either eNom or GoDaddy - and which registrar you use is your choice - though the choice is not made obvious, by the wizard layout.

Wednesday, April 20, 2011

Custom Domain Purchases Not Being Made, Successfully

We get an occasional odd report about a blog, recently setup with a custom domain using "Buy a domain", which cannot be accessed using either the BlogSpot or domain URL. Upon investigation using a Whois log, we see an odd detail.
MYNONXDOMAIN.COM IS AVAILABLE
 
mynonxdomain.com appears to be available
An HTTP trace will appear identical to an improperly published domain.

Upon further discussion with the blog owner, we also learn that the blog owner has seen no charge against the bank account provided for the purchase process. The only sign of the purchase is the BlogSpot URL, redirected to the domain URL.

In this case, the only choice is to publish the blog back to the BlogSpot URL, then repeat the purchase, again using "Buy a domain" - but after diagnosing and possibly correcting your credit card information.

>> Top

Thursday, January 13, 2011

Correcting The GoDaddy Custom Domain Setup Advice

In Custom Domain Setup Advice From GoDaddy Is Wrong, I described the recently updated instructions provided by GoDaddy, to their customers, in Mapping Your Domain Name to Work with Blogger - and I described the observed results.
When investigated, an excerpted Dig log shows a common symptom.
mydomain.com. 3600 IN    A    64.202.189.170
www.mydomain.com. 3600 IN CNAME    mydomain.com.
What we see there is a forwarded domain - and as I have explained a few times, domain forwarding does not produce an effective and reliable custom domain.

Thursday, January 06, 2011

Blog Owners Reporting "The requested URL / was not found on this server. " When Attempting To View Their Blogs

One frequently seen report, in Blogger Help Forum: Something Is Broken, comes from blog owners whose blogs are published to non BlogSpot URLs (though the problem reports may not always mention that detail, explicitly).
Help! I can't see my blog - I just see
The requested URL / was not found on this server.

Thursday, November 04, 2010

Buying A Domain For Your Blog Starts With A Working Major Credit Card

An occasional sad story, from people trying to purchase a non BlogSpot URL for their blogs, results from lack of preparation before using "Buy a domain".
I had my domain all chosen, but when I entered my credit card number, the card was declined. I straightened out the credit card problem with my bank - but now, I get
We found an existing order for this domain.
Help me!

Generally, when this happens, we have the blogger clear cache, cookies, and authenticated sessions, and restart the browser. But this uncertainty is unnecessary, if you have a working credit card ready for use, before you start the purchase process. Paying for your new domain is a major part of the purchase process, so plan and prepare.

Thursday, May 13, 2010

A Domain Purchased Using "Buy A Domain" Is A Fully Functional Domain

Many bloggers are not quite sure about the relationship between Blogger blogs, custom domain publishing, and the "Buy A Domain For Your Blog" wizard.
How do I use my domain with my WordPress blog?
and
Can I use my domain outside Blogger?
and
If I drop my Blogger blog, what happens to my domain?
These are all questions, asked occasionally in Blogger Help Forum: How Do I?

The answer here is quite simple. A domain purchased through Blogger, using the "Buy A Domain" wizard, is a fully functional registered domain. You can do anything with this domain, that you would do with any other domain.