Birk Blechschmidt

I am not sure if this is what you are looking for, but you can use `--retry never`. Then, packets with any response code are printed. However, there is currently...

For JSON, this is implemented by the `e` output format option. (cf60a8e78ea65398be9e7da88db3d953d99263e9) I plan to add this feature to the binary and full output modes as well and will leave...

To debug the issue, I suggest the following: 1. Clone the latest massdns version. 2b394082ea8b45b850718861185194920604e49d fixes an issue, though it is a minor one and only affects mixed resolver lists....

Does massdns show response successes for OK responses? Are you sure it has to do with the output option? I cannot reproduce this. `echo -e "some.invalid.domain\nexample.com" | ./bin/massdns -r tmp/resolvers.txt...

Yes, it is.

In my opinion, massdns should focus on resolving DNS records as fast as possible and return the results with as few modifications as possible. However, since this feature would be...

I cannot reproduce this. On a $5/month Ubuntu droplet in Frankfurt I obtain a success rate of ~3k packets per second with the resolvers from https://public-dns.info/nameservers.txt as downloaded by the...

If implemented cleanly (minimized statefulness, minimum number of memory allocations required), I will accept such a PR. There are basically two options coming to my mind: 1. The use of...

By default, MassDNS treats any rcode that is not `NOERROR` or `NXDOMAIN` as a failure and will retry resolution. (Actually, this has been the default behavior for a very long...

Recently, a paper by the ZDNS authors has been published, in which they compare the performance (table 2): https://lizizhikevich.github.io/assets/papers/ZDNS.pdf While they "configure ZDNS to use 60K threads, a cache-size of...