I think you'll probably find that, averaged out over say a period of 1 hour, an active user will perform at least 1 query every 1-2 seconds.
Twitter, Facebook, anything that uses Ajax and not to mention tons of other CDNs, Ad Networks etc. eat DNS queries like candy and then the underlying OS querying for various services which will inevitably end up at your resolver. Then don't forget IPv6, most of the new browsers already send a query for AAAA at the same time they query for A. Steve On 7 May 2012 14:42, bert hubert <bert.hub...@netherlabs.nl> wrote: > On Mon, May 07, 2012 at 09:13:50AM -0400, Stephane Handfield wrote: > > Hello DNS operators, > > > > I want to know what rules you follow in terms of capacity planning for > your > > DNS. I am mainly interested in the best planning practice for caching > DNS. > > Definitly our rules need to reflect a lots of our own reality, in term of > > agility of deployment, risks, etc. But I'm really interested to know if > > exists any rule of thumb which mostly apply to any situations. > > Here's one. One resolving request per 'broadband residential internet' > subscriber per ten seconds. This is the 'smooth peak nuber'. > > Holds up quite well, although this number is a bit old. It might be eeking > towards one request per five seconds now. > > Adjust width of thumb accordingly! > > Bert > _______________________________________________ > dns-operations mailing list > dns-operations@lists.dns-oarc.net > https://lists.dns-oarc.net/mailman/listinfo/dns-operations > dns-jobs mailing list > https://lists.dns-oarc.net/mailman/listinfo/dns-jobs >
_______________________________________________ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
