Monday, April 23, 2012

Broken processes

Today one of our major clients woke up to no email service.

When planning a company merger our client had grabbed and registered a domain name with a hosting company. Some considerable time later we are helping them to rationalise and move to a smaller number of suppliers. Four previous domain name moves went without a hitch, but mostly because they were not being used and no one noticed that the supplier we are moving from has broken processes...

Simply, their internal process releases a domain name and deletes the record immediately. They should disconnect those two steps because their record delete should only take place after the new host has taken ownership. By doing the delete prematurely there is no lookup for the domain name on any of the Internet name servers and email, web, etc is not able to work.

The problem is that the host we are moving from is being unhelpful, whether out of malice or not. And there is nothing we can do about it. We just have to wait for the new record ownership to percolate through the Internet name servers.

Their customer service is not great; but at least we have the consolation of knowing that we were right to want to make the move!

2 comments:

  1. I've had similarly bad experiences with some domain hosting and registration companies, and we seem to have no redress over their failures to do their job properly. I think the only thing we can do is name and shame until they get some proper industry regulation. My dreadful case is WebMania, based in the UK. Which was yours?

    ReplyDelete
  2. "J" thanks for your comment ... I'm happy to say the host we moved to, Fasthosts, did a first-class job and the move is complete. In this case, though, I'm not going to "name and shame" the other guys. I agree that's often a good tactic, but there's nothing to be gained by it here, and the commercial relationship was with my company's client - They have no axe to grind and don't want to attract the wrong sort of publicity...

    ReplyDelete