DNS measurement failed
Hi, Since yesterday I've been encountering a problem, many of the DNS measurements end with "failed" status. It happens for every measurement that tries to query 8.8.8.8, 8.8.4.4 or when using "Use the Probe's Resolver(s)" feature. However, everything works fine when querying a-dns.pl (194.181.87.156) server. Sample measurements: 3082732 3083505 3083581 Do you observe any issues related to the lack of available probes / exceeded limits? Many greetings, Maciej Andziński, NASK
On Wed, Dec 16, 2015 at 12:00:20PM +0100, Maciej Andziński <Maciej.Andzinski@nask.pl> wrote a message of 20 lines which said:
Since yesterday I've been encountering a problem, many of the DNS measurements end with "failed" status.
Same thing for me. I thought I was the only one. See #3083496 for instance.
On 16/12/2015 12:19, Stephane Bortzmeyer wrote:
On Wed, Dec 16, 2015 at 12:00:20PM +0100, Maciej Andziński <Maciej.Andzinski@nask.pl> wrote a message of 20 lines which said:
Since yesterday I've been encountering a problem, many of the DNS measurements end with "failed" status.
Same thing for me. I thought I was the only one. See #3083496 for instance.
Maciej, Stephane, Can you confirm whether you've seen this problem since 10:12 UTC? That was when a regression was fixed which could have caused this issue. Regards, Chris
Hi, ----- Oryginalna wiadomość -----
On 16/12/2015 12:19, Stephane Bortzmeyer wrote:
On Wed, Dec 16, 2015 at 12:00:20PM +0100, Maciej Andziński <Maciej.Andzinski@nask.pl> wrote a message of 20 lines which said:
Since yesterday I've been encountering a problem, many of the DNS measurements end with "failed" status.
Same thing for me. I thought I was the only one. See #3083496 for instance.
Maciej, Stephane,
Can you confirm whether you've seen this problem since 10:12 UTC? That was when a regression was fixed which could have caused this issue.
I confirm, much better now :) thank you for quick response {"measurements":[3083673]} {"measurements":[3083675,3083676,3083677,3083678]} Many greetings, Maciej Andziński, NASK
On Wed, Dec 16, 2015 at 12:31:08PM +0100, Chris Amin <camin@ripe.net> wrote a message of 49 lines which said:
Can you confirm whether you've seen this problem since 10:12 UTC? That was when a regression was fixed which could have caused this issue.
Apparently, it now works. #3083683 #3083685 #3083690
participants (3)
-
Chris Amin -
Maciej Andziński -
Stephane Bortzmeyer