I just found out a DNS test application that could be run along with nsbench.
namebench provide also results using each user browser history for the DNS lookups or in alternative Alexa top global domains.
Nsbench lookup a well-know domain (google) to minimize request parsing latencies.
namebench instead provide a result based on a dataset that change among users (browser history) or that may change over time (Alexa top domain).
I’m not exactly sure how it works (because the author does not answer questions by email, unless you pay for it…), but you can enter multiple DNS servers and the program connects to all of them (2, in my case) according to the “active connections” shown in CIS. I have no idea whether these are simultaneous requests (like Fastcache does).
The program also uses (if you want) a disk cache. As far as I can tell it writes everything from memory to disk when shutting down the computer (closing the program?). It probably loads these entries to memory when starting again, so that should speed things up a bit.
Deadwood is a working DNS forwarding cache. This is a
server with the following features:
* Small size and memory footprint
* Simple and clean codebase
* Secure design
* Spoof protection: Strong cryptography used to determine the
Query ID and source port
* Ability to read and write the cache to a file
* Dynamic cache that deletes entries not recently used
* Ability to use expired entries in the cache when it is
impossible to contact upstream DNS servers.