But see, it's not even about expecting too much from your host, it's about being on the ball. Like right now for instance, my domain is down because there is an issue with their name server:
Quote:
Searching for rsvip.net A record at J.GTLD-SERVERS.net. [192.48.79.30]: Timed out. Trying again.
Searching for rsvip.net A record at I.GTLD-SERVERS.net. [192.43.172.30]: Got referral to ns36.eukdns.com. (zone: rsvip.net.) [took 146 ms]
Searching for rsvip.net A record at ns36.eukdns.com. [Unknown IP]: Error: Couldn't resolve DNS server name/IP [ns36.eukdns.com][11004]. Response: An error occurred: Couldn't resolve DNS server name/IP [ns36.eukdns.com][11004]. Details: I could not get to the nameserver authoritative for rsvip.net. Sorry!
|
Source: http://www.dnsstuff.com/tools/lookup...vip.net&type=A
Do you think eUKHost have even noticed that one of their name servers is down? And if they have, why didn't they tell me? How long do you think I'll have to wait before this problem has been resolved? So it's not about 24/7 monitoring, 100% uptime, clustering or other fancy options, it's about knowing that a piece of equipment is broken and telling your customer when this happens.
Of course I don't expect 100% uptime, or that all problems are fixed instantly, but I *do* expect that they are on the ball, at least trying to fix stuff or letting me know that they are trying, and I'm getting a little frustrated at the amount of times this isn't the case. Now you tell me if you still think I'm asking for too much.