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

What "Round robin DNS" services do you know/use? I am interesting in free and commercial variants. I have domain and a few ip addresses from each server. But i think that some servers (Windows Sever 2008 R2) can be down from time to time. I found that rrdns can be one of variants to prevent fault of web service. Or could you recommend another tactics?

Thank you for any advice!!!

share|improve this question
up vote 2 down vote accepted

I don't generally approve of RRDNS as a mechanism of increasing fault tolerance. If you really want a great network, then you've gotta start with solid building blocks to begin with..

Do your servers have a diverse route to the internet? Do they have independent power supplies? If you're talking about true fault-tolerance, then you need to start a lot lower down the chain.

  1. Dual (multiple) disks in a RAID layout that isn't RAID 0.
  2. Dual power supplies, provided by dual redundant diverse power feeds.
  3. Dual NICs to separate switches
  4. Dual Firewall/Routers
  5. Dual (or multiple) Internet transit/peering providers, providing routes to the internet via BGP

Then you can start considering multiple datacentres, which is a completely separate kettle of fish. I'm not entirely adverse to RRDNS as a solution to increase redundancy and resilience, but the initial stuff has to come first.

You'll still have the bigger problems, associated with ISPs rewriting short DNS TTLs, which are required for fast-ish failover to a different DNS provider. I spent a good few weeks doing research about the best way to ensure a system's uptime using a combination of network-layer resilience, using BGP, as well as multiple A records in DNS, and RRDNS. In the end, we decided that Dynect were the best DNS provider for our needs, but YMMV, as always.

It's always worth looking a bit deeper than merely the IP address of your server, to ensure that hardware failures can be endured by a combination of RAID, or multiple servers behind a load balancer, and then you can start really looking at scalability/redundancy. If you've only got one server, with one disk, and one nic, and one switch, then it's all a bit pointless looking past that. Just upgrading everything to be a pair will bring some peace of mind.

As a systems engineer, I now can't count any lower than 2.

share|improve this answer
Thank you @Tom! I will keep in mind your advices;) – Edward83 Nov 28 '10 at 21:05 is in the process of implementing rules based dns, you might want to check it out.

share|improve this answer
thank you! – Edward83 Nov 29 '10 at 7:23

Try - simple service but very reliable.

share|improve this answer
thank you) – Edward83 Dec 12 '10 at 18:58

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.