sanity checks during data gathering
Right now it is relativery easy to make a mistake in respdiff/firewall/daemon configuration and find out about the mistake only later during analysis, which is too late because the time and resources were already wasted.
Some lightweight sanity checks should be done during data gathering so misconfigurations can be detected early and users do not waste time and computing power unnecesairly.
Ideas:
-
check that X (or X %) last answers in row are not timeouts -
check that X (or X %) of randomly selected answers exhibit following properties: - other resolvers agree in > 90 % of cases
- target agrees in > 90 % of cases
-
compare results from random sampling and last X answers - there should not be significant difference, especially not a drop in match rate