On Sun, 30 May 2021 at 14:49, Lukas Tribus wrote:
>
> Hello,
>
> On Sun, 30 May 2021 at 14:39, Stephane Bortzmeyer 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:
> >
> > %
Lukas, I just tried as well, and I see no issues:
sanjeev@T450s-disco:~$ blaeu-resolve --requested 100 --area North-Central
--nameserver 8.8.8.8 --type A google.us
Nameserver 8.8.8.8
[172.217.17.100] : 1 occurrences
[142.250.75.228] : 1 occurrences
[216.58.209.68] : 1 occurrences
[142.250.184.4]
Hello,
On Sun, 30 May 2021 at 14:39, Stephane Bortzmeyer 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
>
On Sun, May 30, 2021 at 02:27:18PM +0200,
Lukas Tribus wrote
a message of 41 lines which said:
> while troubleshooting DNS issues on the Google network yesterday [1]
> we found that RIPE Atlas probes did not recover after Google fixed the
> issue, we kept seeing SERVFAIL answers on the RIPE
Dear list,
while troubleshooting DNS issues on the Google network yesterday [1]
we found that RIPE Atlas probes did not recover after Google fixed the
issue, we kept seeing SERVFAIL answers on the RIPE Atlas probes.
We now know that those ATLAS results are bogus.
For example google.us against
