On 20.06.22 17:44, Sten Carlsen wrote:
From my corner of Eurpoa it looks worse.
% time dig www.ecb.europa.eu
[...]
dig www.ecb.europa.eu 0.00s user 0.01s system 0% cpu 8.609 total
With dig +trace it takes longer:
dig +trace www.ecb.europa.eu 0.01s user 0.02s system 0% cpu 1:24.75 total
2, at 17.04, Robert M. Stockmann wrote:
>
> On Fri, 17 Jun 2022, Matus UHLAR - fantomas wrote:
>
>> Date: Fri, 17 Jun 2022 13:04:51 +0200
>> From: Matus UHLAR - fantomas
>> To: bind-users@lists.isc.org
>> Subject: resolving www.ecb.europa.eu tages ages
>>
>&g
On Fri, 17 Jun 2022, Matus UHLAR - fantomas wrote:
> Date: Fri, 17 Jun 2022 13:04:51 +0200
> From: Matus UHLAR - fantomas
> To: bind-users@lists.isc.org
> Subject: resolving www.ecb.europa.eu tages ages
>
> Hello,
>
> I encountered case where resolution of www.ecb.e
On Fri, 17 Jun 2022, Matus UHLAR - fantomas wrote:
> Date: Fri, 17 Jun 2022 13:04:51 +0200
> From: Matus UHLAR - fantomas
> To: bind-users@lists.isc.org
> Subject: resolving www.ecb.europa.eu tages ages
>
> Hello,
>
> I encountered case where resolution of www.ecb.e
> On 20 Jun 2022, at 10:22, Borja Marcos wrote:
>
Looking at it there are also problem affecting the europa.eu domain.
Some servers are sometimes unresponsive over TCP (doing some simple queries
one of them took 5 seconds to answer).
And europa.eu fails to pass the 2020 DNS Flag Day tests.
> On 17 Jun 2022, at 13:04, Matus UHLAR - fantomas wrote:
>
> Hello,
>
> I encountered case where resolution of www.ecb.europa.eu takes long time and
> I can't find out why.
>
> I'm trying to find the culprit using dig +trace and resolution times change
> from < 1 second to > 15 seconds,
DNSViz is usually the go-to tool when trouble shooting
is-it-me-or-is-it-them DNSSEC issues, but it’s thorough enough to help for
a lot more general problems too.
Someone else has been using it to check that name,
https://dnsviz.net/d/www.ecb.europa.eu/dnssec/
The only thing that pops up that
Hello,
I encountered case where resolution of www.ecb.europa.eu takes long time and
I can't find out why.
I'm trying to find the culprit using dig +trace and resolution times change
from < 1 second to > 15 seconds, while response times reported by dig say
miliseconds.
multiple runs of dig
8 matches
Mail list logo
