Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Our business currently subscribes to a DSL internet connection. We're moving away from this and in fact will have two 3Mbps dedicated fiber connections run into our operations center in the coming weeks. The first fiber connection will be ready in 2 weeks, the second in 2 months. My question is with regards to DNS records, specifically in publishing multiple DNS records that point to the same address. When the first fiber connection becomes available I will want to have our domain (www.example.com) point to both it and the old dsl service. I will be using a multi-wan router to handle both connections. When the second fiber connection is installed I will essentially do the same configuration as before, cutting the dsl conn out of the loop. I'm fairly new to DNS and am concerned as to how I might achieve this.

share|improve this question

1 Answer 1

up vote 3 down vote accepted

Just add multiple IN A records, they will be randomly served by your DNS server.

See Round robin DNS on Wikipedia

share|improve this answer
    
So, with two connections... if one connection fails then will every other customer's connection fail or will they experience momentary latency and then be redirected to the still functioning connection? –  JohnyD Sep 23 '09 at 14:01
    
If one connection fails, one of N customers' connection will fail too, N being the number of IN A records. This is due to DNS caching on the client side. When a client resolves a domain, if there are multiple records, there are multiple answers (randomly sorted). The first answer is then cached for TTL seconds. If you don't update your configuration when a host fails, at the end of the TTL, another query will occur, with 1/N chance to get the same host. Round robin DNS is not fail-over ! –  Julien Tartarin Sep 23 '09 at 17:24
1  
"they will be randomly served by your DNS server" is wrong. It depends on the name server (NSD, for instance, does not do it) and, for BIND, it depends on its configuration. Sometimes, the records are randomly shuffled, not by your name server, but by the recursive cache of your clients. –  bortzmeyer Sep 24 '09 at 7:45

Your Answer

 
discard

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.