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/ripe-atlas@ripe.net/
[atlas] DNS probes: spurious SERVFAIL
- Previous message (by thread): [atlas] DNS probes: spurious SERVFAIL
- Next message (by thread): [atlas] DNS probes: spurious SERVFAIL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lukas Tribus
lukas at ltri.eu
Sun May 30 14:49:52 CEST 2021
Hello, On Sun, 30 May 2021 at 14:39, Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote: > > To reproduce, just try to resolve zoom.us or google.us against 8.8.8.8 > > or 1.1.1.1 on your probe. > > It works and I don't see one SERVFAIL: > > % blaeu-resolve --requested 100 --area North-Central --nameserver 8.8.8.8 --type A google.us > ... > Test #30484765 done at 2021-05-30T12:34:54Z That's a major difference to what I'm seeing, and I don't get why the difference is so huge. Just now:1000 probes, area North-Central, A record google.us against 8.8.8.8: Above 90% of ther answers are SERVFAIL (the rest probably is not in yet, or timeout). https://atlas.ripe.net/measurements/30484987/#probes Only 12 (twelve) probes returned NOERROR. Lukas
- Previous message (by thread): [atlas] DNS probes: spurious SERVFAIL
- Next message (by thread): [atlas] DNS probes: spurious SERVFAIL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]