Skip to main content

Posts

Showing posts with the label Custom Domains Schizophrenia

A Domain Root, With Blogger And Non Blogger Hosts

Some blog owners publish a domain, and try to combine a Blogger blog, and a non Blogger website, in the domain root. They publish one host to the domain root - and the other to the "www" alias. This combination may be supported by the non Blogger host - but Blogger blog reliability will suffer. And the readers may become confused, when they click to view the blog, and get the website - or vice versa. There is a special relationship between the domain root and "www" alias . Blogger takes advantage of this relationship, to provide improved reliability for a blog, when published to a custom domain.

What Is "ghs.google.com" vs. "ghs.googlehosted.com"?

With Google Domains registered custom domains becoming more normal, we are seeing one odd attention to detail, expressed as confusion in Blogger Help Forum: Learn More About Blogger . My website uses "ghs.google.com" - am I supposed to use "ghs.googlehosted.com", instead? It's good to be attentive to detail, particularly with custom domain publishing . This is one detail that may not require immediate attention, however.

Don't Try To Split The Custom Domain Root URLs

Some blog owners publish both a blog and a website - and combine the two in the domain root / www host address pair. This technique, while apparently reasonable, will eventually lead to confusion from the blog readers - and / or anguish by the blog owners. Some readers, using a browser or DNS client that aliases the domain root and "www" host , will find that the website will come up, when the blog is referenced, or vice versa. And some blog owners may find, once more, another case of "Another blog ..." / Key already exists ..." , when examining or publishing to the domain. In neither case will the blog owners or readers be pleased.

The Domain Root ("Naked Domain") May Not Be Optional

One of the most consistently seen complaints, in Blogger Help Forum: Something Is Broken , involves blog owners who can't get their blogs working, using custom domain publishing. Thanks to undertrained tech support staff , a common feature at too many registrars, the most common cause of custom domain problems involves failure to use "CNAME" referral - or "CNAME" referral targeting the wrong destination. Both use of forwarding, and "CNAME" referral to the domain root, is seen too often. www.mydomain.com. 1800 IN A 64.202.189.170 or maybe www.mydomain.com. 1800 IN CNAME mydomain.com Please, don't use either of the above address models! Unfortunately, even with the blog properly published to the "www" alias - and with the "www" alias using "CNAME" referral, targeting "ghs.google.com" - we still see problems. With neither of the above mistakes made.

Why Do We Need Four DNS Servers?

Occasionally, we see a perplexed blog owner asking a popular question about custom domain setup. Does my domain really need four servers? Some even seem to think that newer domains, with less readers, can get by with less - even one - servers. Won't one server do - at least, for newer blogs? Theoretically, yes. But not one server is going to be 100% reliable, or last forever. Every computer ever made, like every human born, will die, one day. Your blog (and your domain) depends upon DNS, to resolve its address . Address resolution is an essential part of helping your computer (your readers computers) connect with the computer where your blog is stored.

Custom Domain Instability Caused By Server Mismatch

A few blog owners become confused by the necessary configuration of the domain root, when setting up their custom domains. Some blog owners, who do not have a good understanding of DNS principles, make mistakes when setting up the domain root (aka "naked" domain). From good intentions (trying to ensure that the domain performs better or differently), their naivete may actually make the domain perform worse - or not at all. With more blog owners unable to buy a domain through Blogger , and forced to setup their own DNS addresses, this will become an common mistake , and an increasingly critical issue.

Schizophrenia And Custom Domain URLs - October 2012

Now that the custom domain publishing feature is back online again, there remains one feature of custom domain publishing to be restored to the Blogger dashboard. The very popular Blogger dashboard option to redirect the domain root (aka "naked domain"), to the "www" alias, may not be reliable - or even available . Too many people report I can't redirect the naked domain - I can select the option, but the next time I look, the box will be un checked. and My "www" alias works just fine - but the domain root now returns a "404". Fortunately, there are alternative solutions to provide the naked domain redirect.

Custom Domain Publishing, And Naked Domains

We see several problems weekly, which relate to custom domain redirects. My domain root isn't working! or How do I get my naked domain to redirect to my blog?? Generally, we'll investigate, discover an apparent Google server problem in the original publishing sequence, and recommend recycling of the domain . Sometimes, the solution is simpler - but we may not get to the simple solution, immediately.

Aliasing Of Non Root Custom Domain URLs Ended

Since the beginning of the Google Custom Domain option, the ability to publish a blog to "www.mydomain.com", and optionally have Blogger associate "mydomain.com" with "www.mydomain.com" , has been an assumed feature in custom domain publishing. Similarly, the ability to publish to "blog.mydomain.com", and optionally have "www.blog.mydomain.com" as an association, was an assumed, if slightly less popular option.

Blogger Magic - The Two Queens

If you enjoy single deck card games, such as the magic trick of Three Card Monte , you probably depend upon an unbroken rule. All cards, in a deck, are unique. There can be only one Queen Of Spades. Some blog owners don't accept this rule, when setting up their custom domains. How do I use two domains, with one blog? This question is vaguely similar to swapping domains between one blog - and there is where some confusion starts. I bought a second domain for the blog - and the first domain stopped working!

Schizophrenia And Custom Domain Blogs Published To Additional Virtual Hosts

Long ago, when custom domain publishing was first offered as an option by Blogger, there was a noticeable design deficiency . If you published your blog to the root of the domain ("xxxxxxx.com"), you'd have no content for the "www" alias ("www.xxxxxxx.com") - and if you published to the "www" alias, the root would, similarly, lack content. It was a significant day for many custom domain bloggers, when this discrepancy was eliminated .

Your Blog, Schizophrenia, And The Search Engines

One of my most intriguing subjects (to me, anyway) examines the differences between the "root" alias of a BlogSpot blog, and the "www" alias (ie, "bloggerstatusforreal.blogspot.com" and "www.bloggerstatusforreal.blogspot.com"). The fact that they are separately stored in browser cache will cause mysterious results, when the blog is viewed alternately using the two different aliases . This is not a terrible problem for your readers, when they simply read the blog. It can cause problems with the search engines, though, as they index your blog based upon inlinks from your readers.

Schizophrenia And Custom Domain URLs - March 2009

When you setup a Blog*Spot blog, and publish to "myblog.blogspot.com", Blogger automatically defines "www.myblog.blogspot.com" and redirects it for you, to "myblog.blogspot.com". This is a traditional convenience for your readers, and lets them address the blog as either "myblog.blogspot.com" or "www.myblog.blogspot.com". It's not a built in privilege for all web sites, and neither is the ability to address a non BlogSpot blog as either "www.mydomain.com" or "mydomain.com". A few bloggers don't understand the necessity for the schizophrenic URLs . My readers only need to use "www.mydomain.com". or I don't care about "www.blog.mydomain.com", I only need "blog.mydomain.com" to work. It's possible that, in a differently designed database, "www.mydomain.com" and "mydomain.com" would be two separate, and distinctly unique addresses, capable of working on ...

Custom Domain Publishing, Your Blog, And The Browser

Many bloggers, grown weary of the periodic and unpredictable nature of the ubiquitous Not Found Error 404 and its cousins, the old Another blog is already hosted at this address and the newer Blogs may not be hosted at naked domains errors, are losing their grip. Recently, we see too frequently I tired of worrying about it, just published my blog to www.mydomain.com, and decided to forget about the option Redirect mydomain.com to www.mydomain.com. Imagine my surprise when I typed "mydomain.com" into the browser address window, and up popped the blog! Those of us experienced with this issue simply ask Were you using the Firefox browser? and following the surprised reply Yes, but how did you know? we explain Firefox does this automatically. If Firefox gets a "404" when retrieving "mydomain.com", it automatically tries for "www.mydomain.com", and vice versa. Not all browsers work this way. Anybody using Internet Explorer, Opera, Safari, ... is...

Schizophrenia And Custom Domain URLs - December 2008

Last month, I reported an oddity in custom domain publishing - the observation that, for some domains, the selection Redirect mydomain.com to www.mydomain.com. was apparently treated as selected, even if not so, by some custom domain scripts. A number of bloggers reported seeing "Server Not Found Error 404" for custom domains that had been operational for some time, and subsequently revealed that they were only publishing to "www.mydomain.com", with no DNS address definition for "mydomain.com". In the latter cases, my advice would be Add a DNS address definition for "mydomain.com" (or "www.mydomain.com", as necessary). Wait for the appropriate TTL latency period to expire. Publish the blog back to BlogSpot, then forward to "www.mydomain.com" again.

Schizophrenia And Custom Domain URLs

When you setup a Blog*Spot blog, and publish to "myblog.blogspot.com", Blogger automatically defines "www.myblog.blogspot.com" and redirects it for you, to "myblog.blogspot.com". This is a traditional convenience for your readers. When custom domains were first developed, they didn't provide the same thoughtfulness - the ability to (optionally) redirect "www.mydomain.com" to "mydomain.com" (or vice versa) wasn't added, as an option, until much later, and after a lot of pleading by the blogger community. The great majority of all bloggers consistently select the "Redirect mydomain.com to www.mydomain.com." option, when setting up their custom domain publishing. It's also possible that Blogger has, maybe not intentionally, enabled that option by default, in some (though maybe not all) custom domain scripts. I am trying to use the custom domains option to publish my blog but I keep getting the 'Another blog...

The Trinity, and Your Web Site

The power and majesty of the trinity has been a part of mankind for years, before the Internet. From religion (the Christian nature of the supreme being - The Father, The Son, and The Holy Ghost), to properly robust systems, using triple redundancy (as in Robert Heinlein's science fiction - "I now tell you, three times, to do this!"), the number three has always had almost mystical significance. And with your web site, there is a trinity too. You are using, and may be paying (directly or indirectly) for 3 different services. Registration . DNS Hosting . Content Hosting .

Your Browser Cache, and Web Sites With Dual Addresses

As you surf the web, and read various web sites, you'll occasionally notice oddities. Following one link, you'll see one version of a web site; following a second link, you'll see the same web page, but with different content. Obviously, the web page was updated, between the first time that you visited it, and the second time. Nothing odd there. But here's the oddity. You visit the web site a third time, using the first link, and you see the same, older content. Then you check the second link again, and it shows the newer content again. What's going on here?