Skip to main content

Custom Domains and Case Significance

As I've said repeatedly, Google Custom Domains depend heavily upon DNS.

In the DNS server world, there are two dominant players - Windows (which is provided by Microsoft), and Unix (which is provided by many different players). Just like USA politics (the Democratic party vs the Republican party), USA leading soft drinks (Coco-Cola vs Pepsi-Cola), and other dichotomies, the differences between the players are sometimes subtle (in appearance) but major (in effect).

The Windows vs Unix dichotomy has a major effect on the success of your custom domain.

The BlogSpot alias for this blog is "bloggerstatusforreal.blogspot.com". That's a mouthful, isn't it?

To make the URL of this blog more readable, and maybe get name recognition sometimes, I might spell it as "BloggerStatusForReal.BlogSpot.Com".

In the Unix world, "bloggerstatusforreal.blogspot.com" would not be considered the same blog as "BloggerStatusForReal.BlogSpot.Com". In the Windows world, however, "bloggerstatusforreal.blogspot.com" would be considered the same blog as "BloggerStatusForReal.BlogSpot.Com".

We say that Unix observes case, and that Windows preserves case. You can, if you wish, read the HP white paper, Case Sensitivity versus Case Preservation in CIFS Server, for an in depth discussion of the overall issues.

If Blogger / Google used only Unix servers, it's possible that the two URLs - "bloggerstatusforreal.blogspot.com" and "BloggerStatusForReal.BlogSpot.Com" - could refer to two different blogs. Since many blog owners use Microsoft Windows, Blogger has to consider the two spellings, and other variants - "BloggerStatusForreal.blogspot.com", "BloggerStatusFORReal.BlogSpot.Com", and so on - all refer to the same blog.

Besides the unpredictable nature of the clients (blogger computers), and a possibly relevant assortment of computers running Unix and Windows in the Google infrastructure, there's a third detail - in DNS, Google servers don't function solely as servers.

The DNS servers that we depend up to host our custom domains DNS addresses are the ones that Google depends upon too. Those servers, provides by a variety of Internet entities, will definitely be running a mixture of Unix and Windows.

And there is where one problem starts. The end result is that, if you ask for help, and mention "BloggerStatusFORReal.BlogSpot.Com" or "Blogging.NiteCruzr.Net", I will immediately correct you - and advise you to use "bloggerstatusforreal.blogspot.com" or "blogging.nitecruzr.net".

Comments

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.

Free Domain Registration By "UNONIC" Is Fraudulent

Blogger blog owners, like everybody else, like to save money.

Some blog owners prefer to save money when registering a custom domain, for their blogs. We've seen several free domain registration services, providing what is claimed to be a two level Top Level Domain "co.xx" (where "xx" == various country codes).

The latest in this ongoing story appears to be "net.tf" - and 13 other "top level domains".There is also an additional free service offering third-level .tf domains, under the name United Names Organisation. They occupy 14 second-level domains, including .eu.tf, .us.tf, .net.tf, and .edu.tf. They are run by the same company as smartdots.com, and are given away as URL redirections.