Quote:
Originally Posted by Izzmo
What would be a good way to use all of these?
|
Not sure why you feel the need to??
Quote:
Originally Posted by Izzmo
I called up a guy from my datacenter, and he said he would use a couple for his main hosting website, so even if his clients sites were down, there was a good possibility his main one was still live. How would I go about doing this?
|
Well, I don't really see any logic in that statement. The only potential reason I can see that giving any better resiliency is in the event of routing/network problems. Any other problem which comes to mind would affect the whole server...
However, with routing/network problems it's most likely that the connection to the server will die (e.g. if the switches/routers in the DC have problems) or if it's an external routing issue of some kind a whole block of IPs will be affected - I guess including all 10 of yours at once.
Quote:
|
Or is this even worth it?
|
I think I answered that
Quote:
Originally Posted by Izzmo
Yes, it is easy. But I'm changing the IP on my main website. I can do it, but then it starts showing my default cPanel page (the green one... Welcome to Apache! or w/e) instead of my site.
This is.. if I try to add another IP to the site.
I can get 1 dedicated IP hooked up to my site fine, it's just 2 that I can't get working. Is this possible to do? And.. is it even worth it?
|
This ought to be possible to do, but I don't think cPanel (or any other panel) will let you do this via the interface because - as above - there's not really any point.
I guess that you could just configure Apache (i.e. by manually editing config. files) to serve the same site etc. for 2 IPs, but I can't say that I've ever tried it
If you want to have your website online in the event of problems with your customers websites then you should look to host your own site on a separate server. Generally this doesn't look so good if your site is in a completely different location (i.e. a different datacentre / country) so host the main website on your own server with your customers, then host a support/customer portal micro-site elsewhere.
We have two hosting locations on completely separate networks and our support system is located in a third location. This seems to work well, and our customers like the reassurance this gives. Depending on your needs and budget you could use anything: a solid shared hosting plan, a VPS, or a full dedicated server.
You can do more complicated things with redundancy and mirroring etc. (at a price!) - but if your hosting is that unreliable then maybe you should stop charging people for the service?