I announced last night that I've moved officially moved over to a new domain last night, Yay. But I see you asking, "If you have moved over to Bloggerfocus.com, why are you still using the 4u2invest.blogspot.com url?" I wish it was that simple especially for someone who has no relative experience with DNS or CNAME.
Flashing back to last nite, before I went to sleep, I thought I had managed to get the new domain name running on my site perfectly. Everything seemed to be working fine, blogger.com redirected my blogspot page to the new domain name, the links are working fine after configuring my feed to point to the new domain. I went to sleep feeling rather thrilled and satisfied with my mini achievement. Phewww.
I tried accessing my new domain again after waking up this morning, expecting to see my webpage displayed on it. To my utmost dismay, something else appeared. I was served with a page as shown in the picture below:
What on the earth just happened? Did I not point my CNAME to blogger's server? It must have been something that I've done wrong last night. Some setting that I've done at Zoneedit that has not taken affect until the DNS server for Zoneedit informed the rest of the other DNS servers about the changes while I was sleeping.
You see, last night, I tried using Zoneedit in an attempt to associate my CNAME domain (www.bloggerfocus.com) to ghs.google.com as as per stated in the instruction provided by blogger.com. It was sort of a trial and error thingy with Zoneedit (there was no step by step guide on how to perform CNAME setting in Zoneedit) where I tried different types of setting with my CNAME. I guess one of the settings worked until it got deleted by me when I tried out something else a few hours later.
The bad thing about associating CNAME subdomain, in this case www.bloggerfocus.com, is that you don't see the changes instantly. You've got wait for your changes to be propagated to other DNS servers. That could vary from a few hours to a couple of days. My curious testing with Zoneedit has resulted in my domain name going bonkers, firstly associating with google server and then with some other IP. Boo Hoo.
So I decided to take the hosting of my domain name to a more user friendly 3rd party site in order to try associating again my subdomain to google servers. Lucklily, a simple Google search led me to this FREE domain name hosting site called feeddns.afraid.org.
Thanks to last night's trial and error with Zoneedit, lots of google searches on CNAME and FeedDNS user friendly interface, I believe I've managed to solve my problem once and for all. To confirm whether my associating was done correctly, I use this tool called NsLookup to check. If you see the picture below, my query on NsLookup for www.bloggerfocus.com(the subdomain of bloggerfocus.com) shows that it is pointing to ghs.google.com

Now all there is to do is to wait for FeedDNS DNS server to propagate the changes to the rest of the other DNS servers out there. I hope it will work. Fingers crossed.
Note 20 Mac 3.31pm: Sweet success, I've managed to get http://www.bloggerfocus.com/ up working. Now I'm waiting for blogger to redirect all queries from bloggerfocus.com to www.bloggerfocus.com. This function is offered by Blogger.
Note 20 Mac 3.45pm: Blogger has redirected all queries for bloggerfocus.com to http://www.bloggerfocus.com/. This is great. My blog is back running again.
Note 20 Mac 5.00pm: My site is down again. I still don't understand why. Perhaps I should give it some time. Last check with NsLookup showed that my subdomain still point to google server. Shall leave it for 24 hours and see how it goes.
Note 20 Mac 10.00pm : My blog is back to www.bloggerfocus.com again. Redirected all queries for bloggerfocus.com to www.bloggerfocus.com again. Hope the problem is solved.
Note 21 Mac 1.00am : Thing are not settled yet. I resorted to move my domain name hosting back to Zoneedit. I've just remembered something, some changes that only can be done at Zoneedit.