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] Problems with DNS measurements and NSID
- Previous message (by thread): [atlas] Problems with DNS measurements and NSID
- Next message (by thread): [atlas] Problems with DNS measurements and NSID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.mailinglists at pernau.at
Tue May 20 15:24:17 CEST 2014
Thanks for the hint. Feature Request: Make NSID available in the results (without the need to parse the whole DNS packet). regards Klaus On 20.05.2014 12:52, Antony Antony wrote: > Hi, > NSID is in the result, abuf. I see it when I decode the abuf string. > To decode abuf string you may use a Python script or so. > > https://github.com/RIPE-Atlas-Community/RIPE-Atlas-data-analysis > > "NSID": "tld-berlin-fra1", "OptionLength": 15 > > If you are using the above script better to download it as txt > > wget -O 1666014.txt 'https://atlas.ripe.net/api/v1/measurement/1666014/result/?format=txt' > cat 1666014.txt | ./scripts/decode_abuf.py -dall > > -antony > > > > On Tue, May 20, 2014 at 11:32:39AM +0200, Klaus Darilion wrote: >> Hi! >> >> Whatever I try I fail to get the nameserver id. See measurement: >> https://atlas.ripe.net/api/v1/measurement/1666014/ >> >> But there is no NSID in the results: >> https://atlas.ripe.net/api/v1/measurement/1666014/result/ >> >> Am I doing something wrong, or is there a bug? >> >> Thanks >> Klaus >> >>
- Previous message (by thread): [atlas] Problems with DNS measurements and NSID
- Next message (by thread): [atlas] Problems with DNS measurements and NSID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]