Ron Bennett |
07-17-2008 03:32 AM |
Quote:
Originally Posted by TidalWave
(Post 14469785)
and packet loss relates to the network, not DNS. you should be using your own DNS or a 3rd party dns service.
|
If that's so, then why was their DNS down? ... to me their network problem and DNS problem are two very related things, and thus the OP should be credited for the downtime.
Quote:
Originally Posted by TidalWave
(Post 14469785)
You wernt experiencing "packet loss", you were timing out because the domain wasn't resolving; which they do not have an SLA on. The SLA backs what it says it backs, anything else is not covered and should be considered as being SLA-less and you simply plan based around what you get and don't get.
|
Good point, but this is an instance where it's not as clear-cut as it seems ...
* Presumably he was sold / setup with a server(s), intended for webhosting use, using by default The Planet's DNS for his websites to function.
* He was unable to access the DNS manager servercommand, that presumably resides somewhere else (ie not on his server), on The Planet's network.
* DNS is an integral part of The Planet's network ... I'm assuming the name server addresses used by the OP are the same as those used by The Planet for internal network use ... which appears to be the case, since the OP indicates servercommand was unavailable.
Bottom line this is one worth fighting; esculate it up a few levels, and he'll likely get the credit.
Ron
|