Super User is a question and answer site for computer enthusiasts and power users. 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

I am currently searching for a way to redirect users if my server is down. Is there any way to do such a thing?

Like: If someone wants to connect to my Teamspeak-Server but its offline, it should automatically redirect the user to a Backup-Teamspeak-Server.

Any idea how to realize such a thing?

share|improve this question
I would use keepalived It takes 2 servers and 3 ip-nos. Each server has it's own ip, the third ip points to, keeaplived the makes sure that when your primary server is up it owns the 3:d ip and when your primary server goes down the secondary server takes ownership of the 3:d ip. The details I'll leave to you :-) – Nifle Jan 16 '13 at 18:51

The only way I can think of is setting up an intermediate server which checks the availability of your Teamspeak-Server.

So, the actual URL (say would point to a, for example, PHP page on the intermediate server which would check the status of the actual server and redirect the user accordingly.

share|improve this answer

You could try setting up a round robin DNS setup. Many different ways to achieve this but the wikipedia page will provide you with a starting point.

Round Robin DNS - Wikipedia

share|improve this answer

I've looked around for a solution for Teamspeak in the past. If i remember correct, ts3dns might me useful for you. I can't remember if it does provide the ability to add 2 records (primary, backup) but you could have a 3rd server checking the availability of your servers and set the dns record to the correct server.

Actually you need a DNS server with very low TTL. That could be ts3dns, no-ip like services or even your own custom DNS server who would also check for the availability and respond accordingly.

Have in mind that since Teamspeak doesn't support load balancing, you can not use the round robin DNS setup because people will end up connected on different servers. For the same reason, your server checker should not change the records back to the primary server once the connection is resolved. If you want to do so, you should also connect to the secondary TS server and reboot it so that all the clients get reconnected to the primary one.

Unfortunately, since i needed something easier that that (without needing a 3rd server or external dns services), i ended up setting up 2 subdomains (, for my clan and let everyone know that if the primary server goes down, they should use the 2nd one. They also use the ability to connect on multiple servers so that they would know, when the primary is back online.

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.