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] New on RIPE Labs: Last sponsored RIPE Atlas anchors for 2017
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
dikshie
dikshie at gmail.com
Wed Nov 29 10:14:46 CET 2017
Hi, On Wed, Nov 29, 2017 at 4:27 PM, Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote: > > 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. I see. Previously, I thought using nsid is enough but I found nsid information from my target dns servers are not reliable. There is no way for me to identify the servers. (looks like the dns server operator must fix the nsid text). Best Regards, -- -dikshie-
- Previous message (by thread): [atlas] dig +trace equivalency
- Next message (by thread): [atlas] New on RIPE Labs: Last sponsored RIPE Atlas anchors for 2017
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]