Website hosting redundency
-
Is there a way to have redundancy outside my public ip address? The ip points to my apartment, but say the power goes out in my apartment and my (stupid) isp doesn't battery backup any of their equipment, is there a way to ensure that my site stays online? Talking about hosting in two different spots under what would be two different public ip addresses.
I will also want redundancy on my side of the public ip address so that if a box goes down, the site stays up. Is pfsense able to do this? I poked around in the config and didn't find anything that stuck out right away. I know it can do fail-over for the interfaces and entire router, but I wasn't sure if it could do that for a server behind it.
Thanks for your help!
-
I did find dyndns.com so I got that figured out. Is there a way to have redundant servers on the inside of my firewall?
-
HAProxy may be able to do that.
For automatic failover, DynDNS basic services don't support that, you need the full blown Dynect platform, which is not cheap.
-
I was looking at custom dyndns which I believe does allow that. I'll have a look at haproxy
-
Nope, it allows you to do a manual failover (that is, you have to write all the tools to do it, or visit their site and do it manually). The only part of the DynDNS range that offers automatic failover is the full Dynect platform (not even the Dynect SMB range does). Quoting from their Dynect SMB page (emphasis mine):
Need more? Upgrade to the Dynect Platform.
Looking for geographic targeting? Active failover with global monitoring? Need to share traffic between different Content Delivery Networks (CDNs)? These advanced features are available with a simple upgrade from Dynect SMB to the full Dynect Platform. Simply contact your friendly DynDNS.com support ninja or Dynect concierge for more details on how to get started.
-
If you have your own DNS, some places have done this by having stupidly low TTLs and then having DNS hosted on or updated by the firewall. (I think that's how Barracuda does it).
Relying on DNS for that is asking for trouble though, there's no telling who caches that info longer than you expect them to.
