Thou shall not hasten your domain transfer
April 4, 2008
As I have mentioned in my previous post, I have moved my domains from one host to another not just once but twice. So I am now confident to say that I’m an experienced domain mover. Want to hire me?
Moving a site from host to host could be a very tedious job but there are pointers that you should consider to make the migration process a lot easier. Remember that pointing your DNS to your new host or change of registrars doesn’t mean you have moved your site complete. It does not follow and if you’ll allow me to speak in French, I’d say “Non Sequitur.”
So based from my experience, I’ll be pointing out some pitfalls that I had encountered in the past so you won’t have to experience them. Bad for me that I learn from bad experience but good for you that you don’t have to traverse those paths.
So here goes: Pointers for moving domains
Greetings! Denizens of the cyberspace.
March 31, 2008
I am Blog Almighty, ruler of the cyber world. He who reads me reads the one who wrote me. For man does not read on blogs alone.
Flash update: blogpotions.com is now blog-almighty.com - same blog, different domain. We’re now being hosted by Hostmonster for I believe a Monster Blog deserves a Monster Host. It’s my third host for less than a year you’ll see how fickle my mind is ;-). My first host - Netfirms, I say is a total mess (though I suggest you buy extra domains from them, they’re cheap and DNS transfer is quite a breeze) but for my Dreamhost hosting, I never really had major problems. It’s just that when one of their clustered servers went wrong, I thought I need to have a back up host so not all of my domains will be affected. So now we’re with DreamHostMonster. Got it?
Now I’m claiming this blog to my Technorati Profile while playin Pokemon Red on my GBA emulator ![]()
What panic bloggers need to consider for Web Hosting Solutions
March 27, 2008
I am maintaining several domains under one hosting account with Dreamhost and I haven’t got any problem with that until yesterday.
As I start to browse one of my blogs, I got a “Forbidden Access” error on the index page. I checked my other blogs and the same error message shows. I thought it was only due to my browser or my current location that causes the error until some of my loyal readers informed me that they’re receiving the same error. I logged on to my hosting control panel to submit a ticket to my hosting provider when I noticed this flash notice on their site:
In a way, I felt relieved that there really was a known general server issue and not just something particular to my account (Read: Hacking!). Fortunately the problem only lasted a few minutes in the morning and another few minutes in the evening.
