that any disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited, will be considered a criminal offense, so you must reply to the
> original sender to inform about this communication and dele
Hi,
On 22-11-17, Eduardo Duarte wrote:
> Hi all,
>
> After the recent launch of the Quad9 service I try to discover if it had
> a best response time them my actual resolver, that is google public DNS.
>
> To do this I launch a comparing measurement using atlas that would run
> during one day to t
Hi,
While looking at the result of built-in DNS measurements that use the
probe resolvers, I noticed that a significant fraction of probes have
"127.0.0.1" as a resolver. And the results are strange: performance is
really bad, for instance measurement 30002 gives a median resolution time
of 300 m
s-hijacks-using-ripe-atlas-01.pdf
Yes, I had a look thanks to Vesna: it's interesting but too elaborate for
my needs! The goal here is just to filter out "misbehaving" probes, and
Giovane's method is simple and effective for this.
Thanks,
Baptiste
> - Original Message
Hi Giovane,
On Fri, Sep 29, 2017 at 03:55:21PM +0200, Giovane C. M. Moura wrote:
> > It seems that the "DNS Root Instances" map could be used for that purpose,
> > because DNS traffic interception shows up as if the probe was contacting
> > an "Unknown" root instance. To get the list of probes, I
Hi,
I am looking for a list of Atlas probes that suffer from DNS traffic
interception, to exclude them from my measurements. What I mean by
"traffic interception" is that DNS queries from the probe to a third-party
DNS server do not reach the server, but are intercepted and answered by a
middle-b
Hi Jasper,
On Mon, Apr 18, 2016 at 09:18:49AM +0200, Jasper den Hertog wrote:
> > On 15 Apr 2016, at 18:11, Baptiste Jonglez wrote:
> >
> > I would like to find measurements matching some specific conditions, so I
> > tried to use the measurement API document
Hi,
I would like to find measurements matching some specific conditions, so I
tried to use the measurement API documented here:
https://atlas.ripe.net/docs/rest/
However, filters don't seem to have the intended effect. For instance, I
tried to restrict to a specific range of starting time:
Hi,
Is there a way to reuse and adapt the code for the maps available here?
https://atlas.ripe.net/results/maps/
It could be interesting to have a generic map-based visualisation, where
all probes matching a certain set of conditions would be displayed.
Possible applications include:
- monit
