On Tue, Mar 17, 2015 at 04:15:08PM +0100, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote a message of 4 lines which said:
It seems there is no protection against wrong prefixes?
Last (I promise) remark about prefix selection. I cannot do it from the API. From the Web interface, I can select the prefix 88.176.0.0/12 and it works. But from the API, while it is accepted (I get a number, #1897919), he measurement later fails. My JSON: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of jihadmin.com from prefix 88.176.0.0/12', 'af': 4, 'query_argument': 'jihadmin.com', 'query_type': 'A', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 5, 'type': 'prefix', 'value': '88.176.0.0/12'}]} The status when querying: {u'id': 7, u'name': u'Failed'}