--
>
> *From:* na...@fleish.org
> *Sent:* Monday, January 13, 2025 7:19 AM
> *To:* Mel Beckman ; sterling.dan...@gmail.com dan...@gmail.com>
> *Cc:* North American Network Operators' Group
> *Subject:* Re: Level3 4.2.2.1 and 4.2.2.2 not respo
mailto:North%20American%20Network%20Operators'%20group%20%3cna...@nanog.org%3e>>
Subject: Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries
work
Date: Mon, 13 Jan 2025 14:59:27 -0500
Dan’s not here, man! But I’m glad to spread the word so it can help more people
in their
Dan’s not here, man! But I’m glad to spread the word so it can help more people
in their troubleshoot efforts.
-T
> On Jan 13, 2025, at 10:48, Mel Beckman wrote:
>
> Dan,
>
> That dig tip for identifying the NS phy loc is very nice! That's something I
> can put in our support procedures for
times in milli-seconds:
>> Minimum = 36ms, Maximum = 44ms, Average = 38ms
>>
>> Same for 4.2.2.2
>>
>>
>>
>>
>> -Original message-
>> *From:* Mel Beckman
>> *Sent:* Sun 01-12-2025 06:07 pm
>> *Subject:* Level3 4.2.2.1 and 4
Cc: North American Network Operators' Group
Subject: Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries
work
I’m seeing some of the resolver IPs being filtering from various locations
while responding from others, no doubt due to their use of anycast. I rarely
ping te
packet loss, time 0ms
rtt min/avg/max/mdev = 1.729/1.729/1.729/0.000 ms
"cns1.wdc12"
PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data.
--- 4.2.2.6 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.432/1.432/1.432/0.000 ms
"cns4.sjo1”
oe
Cc: nanog@nanog.org
Subject: Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries
work
Still not pinging from Frontier, Lumen, AT&T, or Verizon networks
-mel
On Jan 12, 2025, at 4:13 PM, Jerry Cloe wrote:
O:\>ping 4.2.2.1
Pinging 4.2.2.1 with 32 bytes of dat
nt = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 44ms, Average = 38ms
Same for 4.2.2.2
-Original message-
From: Mel Beckman mailto:m...@beckman.org>>
Sent: Sun 01-12-2025 06:07 pm
Subject: Level3 4.2.2.1 and 4.2.
sage-
> *From:* Mel Beckman
> *Sent:* Sun 01-12-2025 06:07 pm
> *Subject:* Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS
> queries work
> *To:* nanog@nanog.org;
> I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to
> ping today. They are responding to DNS queries however.
>
> Does anyone know if this filtering is going to be permanent?
>
> -mel beckman
>
>
6:24 PM
To: Jerry Cloe
Cc: nanog@nanog.org
Subject: Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries
work
Still not pinging from Frontier, Lumen, AT&T, or Verizon networks
-mel
On Jan 12, 2025, at 4:13 PM, Jerry Cloe wrote:
O:\>ping 4.2.2.1
Pinging 4.2.2.1
message-
From: Mel Beckman
Sent: Sun 01-12-2025 06:07 pm
Subject: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries work
To: nanog@nanog.org;
I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to ping
today. They are responding to DNS queries however.
Does anyone
O:\>ping 4.2.2.1
Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=44ms TTL=56
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=38ms TTL=56
Ping statistics for 4.2.2.1:
Packets: Sent = 4, Recei
I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to ping
today. They are responding to DNS queries however.
Does anyone know if this filtering is going to be permanent?
-mel beckman
13 matches
Mail list logo
