lucy24 - 9:13 pm on Sep 4, 2012 (gmt 0)
Good. Then the problem is between them and their host. Unless you've got formal authorization to act on their behalf, you couldn't do anything if you wanted to* ;) If it were a DNS issue you'd never even get that far.
But you need to look at the error logs for more information. Even at the generic shared-hosting level, error logs will generally tell you enough to diagnose the problem.
* Assuming for the sake of discussion it isn't one of those "What's a browser?" clients. If so, it will be faster to get authorization and do it yourself than to explain what to do.