The Real Blogger Status

In my first 2 custom domain case studies , I presented actual custom domains - all setup and working. Neither of those exemplify all custom domain setups though. In my previous post in this series, Diagnosing Problems With Custom Domains - Case Study #2 , I showed a custom domain setup using the the "Buy A Domain For Your Blog" wizard . Not too long ago, one setup that way would be not only asymmetrical but incomplete. Let's take a look at a fictional example " mydomain.com ", setup when the the "Buy A Domain For Your Blog" wizard was first provided. There are 4 URLs to study here. The primary domain "mydomain.com". The "www" alias for the domain "www.mydomain.com". The primary BlogSpot URL "myblog.blogspot.com". The "www" alias for the BlogSpot URL "www.myblog.blogspot.com". First, let's dig the DNS records for the primary domain "mydomain.com". ;; QUESTION SECTION: ;mydomain...

If you're currently publishing your blog to a custom domain , because you wanted to use a non-Blog*Spot address with some of the shiny Layouts template features, maybe you're tired of the occasional problems . Maybe you require the automatic redirect from BlogSpot to the custom domain , and the BlogSpot URL is redirecting to a bogus, unwanted warning . Whatever your motivation, it's not hard to go back to publishing on Blog*Spot. Just go to your Blogger dashboard, and click on the Settings link for the blog. Then, from the Publishing link under Settings, select "Switch to: • blogspot.com ". >> Top

The DNS setup shown in my first custom domain case study , "martinezumc.org", isn't typical for all custom domains. That domain, as I showed in my previous post in this series, Diagnosing Problems With Custom Domains - Case Study #1 , was symmetrical - both "martinezumc.org" and "www.martinezumc.org" were defined with "CNAME" referrals, and I could have published the blog to either of the two URLs. When you setup a custom domain while using the "Buy A Domain For Your Blog" wizard , this isn't going to be the case. In this case, the "www" alias will be defined with a "CNAME", but the primary domain won't be. Let's take a look at " nitecruzr.net ". There are 4 URLs to study here. The primary domain "nitecruzr.net". The "www" alias for the domain "www.nitecruzr.net". The primary BlogSpot URL "nitecruzr-dot-net.blogspot.com". The "www" alias fo...

When you work on a custom domain, and the work takes you a few tries while you make one setting, tweak another setting, then republish something, maybe make a change in a post or two, note two issues that may affect your efforts. C a c h e and D N S L a t e n c y . Besides being dependent upon blog content, examination of custom domain publishing also depends upon DNS content. Both blog content and DNS content are subject to caching. Transmission of DNS content from the DNS Host (generally, but not always, provided by your domain registrar) to your local DNS server (generally, but not always, provided by your ISP) is affected by DNS Latency. When you're trying to correct a problem with a custom domain setup, if you want predictable results from any change that you make, you're going to have to deal with both issues. Any change you make may not show up immediately, because of caching and / or latency, and with both issues involved in a given problem, there are possibilities ...

Google Custom Domains, that give us the possibility of having a blog with a non-Blog*Spot address, are a major improvement over plain old Blog*Spot to many bloggers. Occasionally though, problems arise, and diagnosing the symptoms , to allow us to focus on the problems, will require some technical ability, and the right tools . And, note the possible effects of cache and DNS latency , any time that you diagnose or examine a custom domain problem. Here's a baseline study, which will show what you should see as the best possible case. My first custom domain, "martinezumc.org", I was able to setup with 2 "CNAME" referrals. I call this "symmetrically configured". There are 4 URLs to study here. The primary domain " martinezumc.org ". The "www" alias for the domain " www.martinezumc.org ". The primary BlogSpot URL " martinezumc.blogspot.com ". The "www" alias for the BlogSpot URL " www.martinezumc.bl...

When "Beta" Blogger, later known as New Blogger 2006, was first rolled out, there were many new features, and improvements over "Old" Blogger, noted. There was also one feature, that was not seen as an improvement, noted. When you include any indenting block of text in your blog post, <blockquote> ... </blockquote> <ol> ... </ol> <ul> ... </ul> for instance, the spacing of the posts, below the indenting block, would change. This makes the entire blog look sloppy. Several workarounds were identified by various bloggers; not any one was simultaneously clean, effective, and simple, however. After repeated complaints and reports, Blogger finally acknowledged the problem . Yet, it's still not fixed. Blogger calls it " Cosmetic ". We call it sloppy. >> Top

The title of this blog is "The Real Blogger Status". This blog contains many posts. The name of this blog is "bloggerstatusforreal", and its URL is now " blogging.nitecruzr.net " (it's also known as " bloggerstatusforreal.blogspot.com "). There can be only one BlogSpot blog with the name "bloggerstatusforreal", though there can also be "bloggerstatusforreal.com", and "bloggerstatusforreal.net", and each can be separate web sites, if desired. And any blog can have the title of "The Real Blogger Status".