Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

We are considering to self-hosting for a domain. How can we provide a page to visitors in case of failure, such as loss of network connectivity, server failure or power failure?

share|improve this question

closed as too broad by womble, Ward, masegaloeh, ErikE, Falcon Momot Aug 25 '15 at 0:50

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

Note that this is loosely related to this ServerFault question: – Justin Scott May 11 '09 at 13:20
What I did when faced with the same requirement was to rent four servers at four different hosting providers to serve as independent replicas for our zone. – kasperd Oct 22 '15 at 19:39

This was asked and answered over on Stackoverflow. Summary, you can't reliably do this with DNS, but there are approaches that mess with BGP routing to accomplish this.

However, if you're just interested in handling local failures to your solution, and you are assuming your hosting company is still up and providing service, you can ask them - they may have the capability in their load balancers etc to be able to redirect to somewhere else in their environment.

share|improve this answer

You can't do this with DNS out of the box.

You could use an external DNS server which monitors the page and delivers other DNS information with a low TTL in case it cannot reach the site. BUT this will not work reliably and will also depend on the cache size of DNS servers of clients, and could cause your real site not to be reachable once it is back up due to existing DNS cache entries for the down-site.

share|improve this answer

You can use a service like DynDNS to easily change the IP a domain points to. And, they have an API too, so you could use another cheap webhost to verify when the server is down and change the IP, maybe to that same webhost where you can show a maintenance page.

Or, you can install one of the clients that automatically uses a downtime page.

And you can set a low TTL so IP changes propagate more quickly.

share|improve this answer
We have considered dyndns, but how reliable are they. Will it not just be a chicken/egg problem then? – Tom May 11 '09 at 18:18
They're extremely reliable per my experience. Been using them for more than 5 years and zero downtime. – Ivan May 11 '09 at 22:09

You could host your main domain on a commercial provider and create a page that shows the error message with javascript after a timeout. Then you could include a in the HTML-code. This code would redirect (an frame?) to the real page. Otherweise (javascript-timer?), the error page would be displayed

Now, can I just downvote this answer many times? ;-) Technically it would be a solution given that not so much was cleraly defined in the question. The reason to host in house might be to hook up some internal database, while the main web presence would better be on a commercial hoster.

share|improve this answer

A similar question was asked, and answered here

The short answer is, DNS is not a reliable mechanism for managing failover without significant hardware investment, or manual intervention.

share|improve this answer

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