Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here's what I have to work with:

  • Root access to VPSes with different hosting companies that run CentOS only
    • Two dedicated nameservers with over 100 zone entries
    • Several webservers hosting the same content

The failover solutions I've found either require hardware, clustering in the same network, and other options that I can't access with my VPS setup. And paid DNS failover services are too expensive for the number of domains I have.

It seems implementing DNS failover myself is my best option, though the consensus is that it's not a very good option. Are there ANY other solutions I'm missing? Thanks.

share|improve this question
up vote 2 down vote accepted

You could use Linux IP Virtual Server using tunneling. No need for the "real servers" (webservers) to be on the same subnet.

The ipip encapsulated packages will be ordinary packages that can be firewalled and forwarded.

keepalived is a great tool to handle the service checks and adding/removing failed "real servers"

share|improve this answer

You can use two dedicated 'entry point' VPS servers running a load balancing software like HAProxy. If there are no geographical constraints, i.e. keeping content close to users or so, you can make all dns/http requests land on the load balancing servers and from there send them to the respective webservers.

There are really cheap services like easyDNS or dyndns where you can delegate DNS availaiblity problem :)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.