[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 ]
Daniel Quinn
dquinn at ripe.net
Wed Sep 25 12:35:43 CEST 2013
On 09/24/2013 01:05 PM, Klaus Darilion wrote: > Hi! I managed to create DNS measurements via the REST API, but fail to > set the DO and protocol:TCP option. According to the documentation > (https://atlas.ripe.net/doc/measurement-creation-api/) the relevant > properties are use_EDNS0 and use_tcp. So I tried it with This was a mistake in our API (my bad). There was some confusion as to what should be used (|use_EDNS0|, |use_DO|, |do|, etc.) and it caused some unpredictability in the code. I have now gone through and (hopefully) changed everything to use |do| and nothing else. I've also updated the API doc. So, for the record, the request that started this thread should look like this: |{ "definitions": [ { "is_public": true, "is_oneoff" : false, "target": "194.0.25.13", "description": "a.dns.nic.versicherung_IP4_TCP_noDO", "type": "dns", "af": 4, "interval": 300, "use_TCP": true, "use_probe_resolver": false, "use_NSID": true, "query_class": "IN", "query_type": "SOA", "query_argument": "versicherung", "udp_payload_size": 1024, "protocol": "TCP", "do": true } ], ... }| If there are questions, or if you think that I've missed something, just let me know :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20130925/74d1850c/attachment.html>
- 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 ]