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/[email protected]/
[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 ]
Klaus Darilion
klaus.mailinglists at pernau.at
Thu Sep 26 11:08:28 CEST 2013
Hi Daniel! Thanks for the fast response. The usage of 'do' works now fine and the description is consistent with the usage. However there are still problems with 'protocol'/'use_tcp'. According to the API description, the property to use is 'use_tcp'. And using this property works when creating measurements. E.g. "use_tcp": "true", "protocol": "UDP", will use TCP for querying. But when reviewing the measurement, the property is called 'protocol', e.g. see https://atlas.ripe.net/api/v1/measurement/1028085/ <object> <status type="hash"> <id type="integer">1</id> <name>Scheduled</name> </status> <protocol>TCP</protocol> ... IMO, this should be consistent too. Thanks Klaus On 25.09.2013 12:35, Daniel Quinn wrote: > 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 :-) >
- 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 ]