This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] dig +trace equivalency
- Previous message (by thread): [atlas] dig +trace equivalency
- Next message (by thread): [atlas] dig +trace equivalency
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Wed Nov 29 09:24:00 CET 2017
All, Stephane Bortzmeyer: > On Sat, Nov 25, 2017 at 02:12:06PM +0900, > dikshie <dikshie at gmail.com> wrote > a message of 11 lines which said: > >> I use to use +trace option in dig command. >> Is there any same function equivalency in Atlas's DNS measurement tool? > > dig +trace is not very reliable, and does not work with all > resolvers. And, no, I don't think there is an equivalent for the Atlas > probes. It would require some resolver-like logic in the probe. It is in principle possible to simulate resolver-like logic without updating the probe. In fact, I worked on a team to do just that at a RIPE Atlas Hackathon a couple years ago. You can see the results on GitHub here: https://github.com/shane-kerr/ripe-atlas-shrugd This was just a hack, but the technique should be usable to do something similar to "dig +trace". Cheers, -- Shane
- Previous message (by thread): [atlas] dig +trace equivalency
- Next message (by thread): [atlas] dig +trace equivalency
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]