On 2017/12/03 17:36 , Stephane Bortzmeyer wrote:
> Atlas rejects 'use_probe_resolver': False if you did not specify a
> target:
>
> Status 400, reason
> "{"error":{"status":400,"errors":[{"source":{"pointer":"/definitions/0"},"detail":"`target`
> cannot be null if `use_probe_resolver` is not
>
On Fri, Dec 01, 2017 at 03:44:22PM +0100,
Tim Wattenberg wrote
a message of 123 lines which said:
> In my measurement I activated the option to use the probes
> resolver(s) and left the option to resolve on the probe deactivated.
The documentation
Robert, thanks for your explanations. I now do understand this for all
measurements exept for those of type DNS.
DNS measurements with a central resolver somehow seem not that useful to
me. Am I missing the use case here?
Context: I want to measure the consistency of DNS records or how they are
On 2017-11-30 20:27, Tim Wattenberg wrote:
> Hi everyone,
>
> I think I don’t quite understand the effect of the „Resolve on Probe“ option
> when creating a measurement. The form says it forces the probe to do DNS
> resolution, the API reference says that it indicates that a name should be
>
Hi everyone,
I think I don’t quite understand the effect of the „Resolve on Probe“ option
when creating a measurement. The form says it forces the probe to do DNS
resolution, the API reference says that it indicates that a name should be
resolved (using DNS) on the probe otherwise it will be