--
>
> *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
The 4's have definitely had occasional ICMP allergies over the last 20
years.
On Sun, Jan 12, 2025 at 11:27 PM Mel Beckman wrote:
> Dan,
>
> Thanks! I had never read that before. But that makes sense.
>
> -mel
>
> On Jan 12, 2025, at 8:22 PM, Daniel Sterling
> wrote:
>
>
> Seems like these I
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
Dan,
Thanks! I had never read that before. But that makes sense.
-mel
On Jan 12, 2025, at 8:22 PM, Daniel Sterling wrote:
Seems like these IPs not responding to ping is not unusual, as per
https://www.reddit.com/r/sysadmin/comments/11syv2e/google_dns__dropping_pings_like_crazy_today/
Seems like these IPs not responding to ping is not unusual, as per
https://www.reddit.com/r/sysadmin/comments/11syv2e/google_dns__dropping_pings_like_crazy_today/
"Google has stated multiple times before as has Level3/CenturyLink/Lumen
that 4.2.2.1 and 8.8.8.8 should not be used for ping check
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
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 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: byte
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
12 matches
Mail list logo
