[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 17:08:47 CEST 2014
Hi Daniel! On 20.05.2014 15:43, Daniel Quinn wrote: >> Feature Request: Make NSID available in the results (without the need to parse the whole DNS packet) > > In case you're using Python, you should know that if you use the new > parsing library[1] the work of parsing the DNS packet and getting the > NSID out is done for you: Actually I tried it today but failed obviously due to my lack of Python. It would be great if you could add an example to the README e.g. with full result parsing: - load the json file from disk - loop over every result (json list) - print some value > from ripe.atlas.sagan import Result > result = Result("your-JSON-result-blob-here") > print(result.responses[0].edns0.options[0].nsid) Why do I have to use the responses[0] object? Can there be multiple responses with different nsids? 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 ]