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

If I create multiple DNS A records for the same hosts, for example:   A   3600s   A   3600s   A   3600s
  1. Do queries really round robin between the three servers? Is it even?

  2. Let's assume a client requests and gets back Is that then cached for an hour, so every request the client makes will use, or will each request grab a random host?

  3. What happens if goes down, does DNS automatically take it out, or will requests still route to it in round robin fashion?

share|improve this question
up vote 2 down vote accepted

Yes, you can implement some load sharing using multiple DNS records for the same service. However, this is not the best way to implement load sharing especially in case you have all your hosts reside in the same location. A far more efficient approach will be to use a dedicated machine as load balancer. This machine receives all traffic and forwards it to one of the real servers based on several criteria such as:

  1. Concurrent connections.
  2. Server load.
  3. User source IP.
  4. Round robin.
  5. Weighted round robin, etc...

Another important point in load balancers such as haproxy is the ability to check for failing node and exclude it from the servers list and this is not available in DNS-based method.

Also, DNS caching makes things more complicated and difficult to manage. DNS caching can occur in any node from your client to any intermediate DNS server till reaching the authoritative DNS server.

share|improve this answer
  1. Yes, it will round robin between the three. For windows server DNS, you need to enable Round Robin in your DNS server. When enabled, it will respond with all three records in a rotating pattern:

    • 1st client -,,

    • 2nd client -,,

    • 3rd client -,,

  2. This depends on the implementation on the client side. Some clients will rotate between the records per connection, and some will tend to use the first address received. The load is still balanced since the second client above would have a different ordered list than the first.

  3. If were to go down, it would not be automatically removed. Clients would still attempt connections on that IP. This is the drawback of Round Robin DNS.

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.