3 ms·
For easy comparability, request handling rates of tools like this are best described in terms of requests per second, not requests per hour. Also the hardware
by otterley 10y ago
For easy comparability, request handling rates of tools like this are best described in terms of requests per second, not requests per hour. Also the hardware on which the benchmarks were performed needs to be described in detail.
Are you sure tinydns, which has existed for ages without security vulnerabilities, can't trivially handle 27k requests/second on modern hardware?
- blechschmidt 10y agoI have not heard about tindydns before but it seems to be a DNS server, not a client. The tool has mainly been tested on a Hetzner EX41 server. (Ubuntu, Intel® Core™ i7-6700, 32 GB RAM)
- otterley 10y agoAh, you are correct. There is also dnscache, which is part of the same suite. However, it does not do what you are attempting to do.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- otterley 10y agoHave you tried c-ares? http://c-ares.haxx.se/ http://c-ares.haxx.se/
- blechschmidt 10y agoNot yet. I have had a quick look at ldns (https://www.nlnetlabs.nl/projects/ldns/ https://www.nlnetlabs.nl/projects/ldns/) which supports parsing DNS packets from wire. I will probably replace the DNS implementation with either libldns or c-ares.
- otterley 10y agoldns is synchronous so all your queries will block. libunbound (https://www.unbound.net/documentation/libunbound.html https://www.unbound.net/documentation/libunbound.html), like c-ares, is an async C resolver library from the authors of ldns.
- blechschmidt 10y agoAh, that would mean that I would have the libraries handle the resolving. I was currently only thinking about keeping the single socket which is used in order to only use the parsing functions from the libraries.