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] REST API Problems for DNS measurements with DO and TCP
- Previous message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
- Next message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Wed Sep 25 10:17:44 CEST 2013
On Tue, Sep 24, 2013 at 01:05:34PM +0200, Klaus Darilion <klaus.mailinglists at pernau.at> wrote a message of 57 lines which said: > Hi! I managed to create DNS measurements via the REST API, but fail > to set the DO and protocol:TCP option. TCP worked for me (launched from the API). See public measurement #1025096, TCP is set. I just tried again (public measurement #1027850) with the attached program, launched as: python perf-dns.py -t -6 2001:678:c::1 and it seems to work
- Previous message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
- Next message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]