Is there any RIPE policy about whether nodes that are subject to DNS
interception should be excluded from results (or maybe even dropped
altogether) ?

While these probes are perhaps still useful for ping and traceroute
tests, they are effectively useless for DNS related tests other than as
a proxy measure for how prevalent that practise actually is.

For the visualisation I've just been building based on the Root System's
"hostname.bind" data returned by Atlas it was pretty difficult to figure
out how to exclude those probes on the client side.

If there was a heuristic that could be applied on the probe itself or
within the RIPE data collector that tagged the probe as having "bad DNS"
that would help a lot.

cheers,

Ray Bellis
Director of DNS Operations, ISC.

Reply via email to