On Wed, 24 Aug 2005, Tapio Sokura wrote: > I think the day is near for a special DNS server software that really > does load balancing and maybe even takes into consideration where the > DNS requests come from (= geographically aware). I guess Ask already had > some plans for this?
This topic pops up fairly often btw, have a look at the archives of this list. I think the objectives are: 1. Make sure bad servers are promptly removed from the pool (ie TTL is low) 2. Make sure that a DNS query for a zone is evenly spread across all good servers in that zone. > I don't think it would be much of a problem to have > to run special DNS server software on the secondaries as well. If the > current secondaries can't do it, we'll just have to find ones that can > a) run a special DNS server software and b) can deal with the DNS query > load. As one of the people running DNS software the DNS load isn't that high. Probably we don't need any real special DNS software. At the simplist level the central checker would send out the members of each pool at regular ( 10 minutes say) intervals. Each name server would then randomly populate the pool using avaialble servers. As long as the serial numbers are in sync (not that hard considering ) the number of machines in the pool at any one point should increase by 4 or 5. Using things like views in bind can increase this further. I'd be happy to do some testing. > We now know that the NTP requests themselves average at under 10 packets > per second. But how about the DNS requests foor pool servers? Has > someone running a pool DNS server measured the amount of DNS queries > seen, maybe even gathered some longer term data? I should tidy up my DNS logging... A quick check shows an average of around 5 lookups per second. -- Simon J. Lyall. | Very Busy | Mail: [EMAIL PROTECTED] "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
