Do Not Bridge

I’m getting into LinkedIn these days. There’s a discussion that is broadening out, which reminded me of an old blog post I had on an early blog site I maintained. Not having replicated that post on this blog, I am responding to the LinkedIn discussion here (http://lnkd.in/9qnq9w).

I recommend that you separate domain registration from web hosting.

Why? If you ever need to change web hosts, you can.

The issue is access to your DNS settings.

If your domain registration and hosting is with the same outfit, then you run the risk of not having access to your DNS settings when your web hosting goes down. Why? Because both domain and hosting administration reside within the same control panel. When you cannot access your website admin (not to be confused with your Joomla admin), you lose access to your DNS admin. No DNS admin, no ability to change your host. So, you cannot backup your site to another host because visitors will never be routed to it.

I do not even bother researching if a webhost separates their domain registration from their website administration. I separate domain registration from hosting.

Over the years, I’ve had cases where clients were held hostage by their consultant. They put domain registration, hosting, and consulting in one person’s hands. Very Bad! Separate all three. And do domain registration and hosting yourself. Do not delegate ‘em! One thing you want to avoid is your webhost (never mind consultant!) controlling your domain when there is a dispute about your website. Your inability to change DNS gives your webhost enormous leverage.

I’ve made a few people angry over the years when I refused to register their domain on their behalf. I tell them that it’s better for them to go through the pain of learning how to do register and manage their domains themselves, then to delegate to me.