On 7/25/23 00:56, Stephane Bortzmeyer wrote:
The "abuf" is always in there, so consumers of the results can parse
that (as you already know, and as Seth does below). There are abuf
parsers out there, and if you're using Python then I'd recommend
using Sagan
Or use Blaeu
<https://labs.ripe.net/author/stephane_bortzmeyer/creating-ripe-atlas-one-off-measurements-with-blaeu/>:
% blaeu-resolve --measurement-ID 57629583 check.ns1.dtc.dnssec.lab.nic.cl.
[::2] : 3 occurrences
[] : 1 occurrences
Test #57629583 done at 2023-07-25T00:15:02Z
Also if you happen to have a GCP account, the bigquery interface has a
view that tries to decode the abufs:
> select *
> from `ripencc-atlas.measurements.dns_decoded`
> where date(start_time) = "2023-07-25"
> limit 100
You can filter down to your own measurement ID if you like, though as a
platform it's probably better aligned to work with all the abufs within
a timespan.
S.
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
