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] How to get DNS return codes and TTLs
- Previous message (by thread): [atlas] How to get DNS return codes and TTLs
- Next message (by thread): [atlas] No data for ping to second hop?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Thu Jun 9 09:13:07 CEST 2022
On Wed, Jun 08, 2022 at 06:16:30PM -0600, Dallan Adamson <dallanadamson at gmail.com> wrote a message of 39 lines which said: > I'm doing research that requires me to use DNS recursive resolvers > around the world. At a minimum from these recursive resolvers I need > to know what return code the probe received from the recursive > resolver as well as the TTL of the record from the same request. I > haven't found a way to get both of these when doing DNS measurements > with Ripe Atlas probes, is there a way to do this? Some DNS information is parsed by Atlas and returned in the JSON answer (such as the length of the various DNS sections) but, if you want all the DNS data, you'll have to parse yourself the DNS blob included in the JSON answer (field "abuf"). You can get inspiration from the source code of the official client, or from Blaeu's blaeu-resolve <https://framagit.org/bortzmeyer/blaeu>.
- Previous message (by thread): [atlas] How to get DNS return codes and TTLs
- Next message (by thread): [atlas] No data for ping to second hop?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]