[atlas] What is the meaning of 127.0.0.1 as probe resolver?
- Previous message (by thread): [atlas] Plan to Implement RIPE Atlas WiFi Measurements
- Next message (by thread): [atlas] What is the meaning of 127.0.0.1 as probe resolver?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Baptiste Jonglez
baptiste.jonglez at imag.fr
Fri Oct 13 19:19:30 CEST 2017
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 ms for these probes! What could be the meaning of this? It almost looks like a recursive resolver with no cache at all is running on the probes themselves. I was looking at this measurement: https://atlas.ripe.net/measurements/30002/ And here are some example probes that exhibit this "127.0.0.1" symptom: 6001, 6087, 6162, 6235, 6308. Any reasonable explanation is welcome! Thanks, Baptiste -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20171013/d2ca13d6/attachment.sig>
- Previous message (by thread): [atlas] Plan to Implement RIPE Atlas WiFi Measurements
- Next message (by thread): [atlas] What is the meaning of 127.0.0.1 as probe resolver?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]