Level3/Lumen DNS IP’s

porkapatamus

Can any of you other Comcast users ping Lumen’s (formally Level3) infamous DNS IP’s of 4.2.2.1-6 ? I just noticed I can’t ping them anymore starting a couple weeks ago, and I’m not sure if it’s just my area, or if they blocked all Comcast IP’s. They still work as DNS resolvers, I just can’t ping them, so strange. Thanks all!

ka2107

porkapatamus

% ping 4.2.2.1
PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data.
^C
--- 4.2.2.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9107ms

% ping 4.2.2.2
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
^C
--- 4.2.2.2 ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11157ms

% ping 4.2.2.3
PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data.
^C
--- 4.2.2.3 ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11149ms

% ping 4.2.2.4
PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data.
^C
--- 4.2.2.4 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13189ms

% ping 4.2.2.5
PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data.
^C
--- 4.2.2.5 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12149ms

% ping 4.2.2.6
PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data.
^C
--- 4.2.2.6 ping statistics ---
20 packets transmitted, 0 received, 100% packet loss, time 19248ms

CommunityMember

porkapatamus

Level3's dns resolvers have a (decade+) long history of only sometimes being icmp pingable, and sometimes only from some locations (the servers are anycasted, so there are many servers across their footprint, and you get the one (network) closest to you that is currently operational (individual servers may go offline, but then the load goes elsewhere)).

Many of the public dns providers, as part of their best practices, have various network protections and rate limits on their infrastructure, and as icmp ping is not part of the service, it will sometimes have been limited (and restricted). The more people that try to use a public dns provider as an icmp ping target the more likely it works for no one (or only intermittently when others stop their incessant pings).

SuperNet

No, I can't ping them also.
C:\Users\Owner>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

payup

Pingable from 7018

payup

4.2.2.2 Is still responding to DNS queries from Comcast (AS7922) , Confirmed using RIPE probes.

payup

4.2.2.2 is now responding to ICMP from Comcast

EnasYorl

ping 4.2.2.1

Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=27ms TTL=57
Reply from 4.2.2.1: bytes=32 time=27ms TTL=57
Reply from 4.2.2.1: bytes=32 time=31ms TTL=57
Reply from 4.2.2.1: bytes=32 time=29ms TTL=57

Ping statistics for 4.2.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 31ms, Average = 28ms

kenward1

It works for me.

C:\Windows\System32>ping 4.2.2.1

Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=28ms TTL=57
Reply from 4.2.2.1: bytes=32 time=30ms TTL=57
Reply from 4.2.2.1: bytes=32 time=30ms TTL=57
Reply from 4.2.2.1: bytes=32 time=29ms TTL=57

Ping statistics for 4.2.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 30ms, Average = 29ms

C:\Windows\System32>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=29ms TTL=57
Reply from 4.2.2.2: bytes=32 time=30ms TTL=57
Reply from 4.2.2.2: bytes=32 time=29ms TTL=57
Reply from 4.2.2.2: bytes=32 time=30ms TTL=57

Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms

SuperNet

it works for me now