Need Some People to Do a Ping Test

ZeeOSix

$100 site donor 2022
Joined
Jul 22, 2010
Messages
40,069
Location
PNW
In another thread I discussed my modem showing a self diagnostics test result of "FAIL" for the two CenturyLink DNS servers that the modem uses. If I ping them in a DOS window they seem to be very flaky and DNS #1 (primary server) usually has at least one "time out" in the 4 packets. DNS #2 pretty much always has all 4 packers "time out".

So I'm thinking this is the reason my modem's self diagnostics test shows a fail. I spent over an hour live chatting via computer with a CenturyLink tech and brought all this up. He checked and did every test he could do on his end and claimed everything was working good. I asked him to ping the DNS servers and claims it's OK. I don't think it is, and a couple other members here pinged them and saw time outs.

I think the time outs is why the modem's self diagnostics test shows a fail for the DNS addresses. Something is not right if a ping test doesn't come back clean, and if people all across the country can't get clean pings then it can't be something specific to my system.

So I was wondering if I could get about 10 guys here to do a ping test in a DOS command window for me and let me know what you get. Thanks in advance!

The DNS server address are: 205.171.2.25 and 205.171.3.25

In a DOS window, simply type: ping 205.171.2.25 or ping 205.171.3.25 (one at a time).

This is an example - the ping test ran twice for each DNS address.

205.171.2.25 always times out:
[Linked Image]


205.171.3.25 only sometimes times out:
[Linked Image]
 
Pinging 205.171.2.25 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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



Pinging 205.171.3.25 with 32 bytes of data:
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49

Ping statistics for 205.171.3.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 6ms, Average = 5ms
 
I got the same as above.

You can use Cloudflare DNS: 1.1.1.1 and 1.0.0.1
See if that works for you.

You don't need to use your ISP DNS if it does not work.
I don't use Spectrum DNS, I just used Cloudflare.
 
Last edited:
Originally Posted by ctechbob
Pinging 205.171.3.25 with 32 bytes of data:
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49

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


Forgot to say, if someone pings 205.171.3.25 and it shows 100% solid like above, please ping it again three of four more times and see if it shows any time outs.
 
$ ping 205.171.3.25 -c 10
PING 205.171.3.25 (205.171.3.25): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 205.171.3.25: icmp_seq=3 ttl=53 time=14.868 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
64 bytes from 205.171.3.25: icmp_seq=6 ttl=53 time=17.152 ms
64 bytes from 205.171.3.25: icmp_seq=7 ttl=53 time=15.754 ms
Request timeout for icmp_seq 8

--- 205.171.3.25 ping statistics ---
10 packets transmitted, 3 packets received, 70.0% packet loss
round-trip min/avg/max/stddev = 14.868/15.925/17.152/0.940 ms
$ ping 205.171.2.25 -c 10
PING 205.171.2.25 (205.171.2.25): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- 205.171.2.25 ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
$
 
I am not sure your test is valid if you are relying on ping . Many providers block ping from working by suppressing ICMP, but this usually shows up as a 100% failure.
Pinging 205.171.2.25 for me always fails.

Here is my nslookup on that IP-
Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\System32>ping 205.171.2.25

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

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

C:\WINDOWS\System32>ping 205.171.3.25

Pinging 205.171.3.25 with 32 bytes of data:
Reply from 205.171.3.25: bytes=32 time=9ms TTL=54
Reply from 205.171.3.25: bytes=32 time=9ms TTL=54
Reply from 205.171.3.25: bytes=32 time=9ms TTL=54
Reply from 205.171.3.25: bytes=32 time=9ms TTL=54

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

C:\WINDOWS\System32>ping 205.171.2.25

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

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

C:\WINDOWS\System32>

C:\WINDOWS\System32>nslookup
Default Server: Fios_Quantum_Gateway.fios-router.home
Address: 192.168.1.1

> 205.171.2.25
Server: Fios_Quantum_Gateway.fios-router.home
Address: 192.168.1.1

Name: redirect2.qwest.net
Address: 205.171.2.25


>
 
Last edited:
Originally Posted by rubberchicken
I am not sure your test is valid if you are relying on ping . Many providers block ping from working by suppressing ICMP, but this usually shows up as a 100% failure. Pinging 205.171.2.25 for me always fails.


The ping test results of others here pretty much shows the same thing I do - flaky results on xx.3.25 and complete fail on xx.2.25. I also did a "Traceroute" test from within the modem's utilities and 205.171.2.25 did like 30 "hops" and only the first 3 out of 30 hops showed valid information ... the other 27 hops showed "N/A" for the data fields.

Just seems like the CenturyLlink DNS servers are flaky, and probably the reason the modem shows a "Fail" for the DSN diagnostics part of the built-in test. I would imagine if the self diagnostics test sees any time outs it's going to show as a "Fail" test result.

The weird thing is my internet works fine, and the download and upload speeds all look fine. The CenturyLink tech couldn't find anything wrong and he was doing some tests from his side over the hour+ I was on live chat with him.
 
Originally Posted by OVERKILL
You should run DNS Bench against it, LOL!!!

https://www.grc.com/dns/benchmark.htm


Did you run it? I'm betting it doesn't look good. I can't believe the CenturyLink tech I was live chatting with didn't find anything wrong when he pinged those DNS servers.
 
Pinging 205.171.3.25 with 32 bytes of data:
Request timed out.
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Request timed out.
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Request timed out.
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Request timed out.
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Request timed out.
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49
Request timed out.
Reply from 205.171.3.25: bytes=32 time=5ms TTL=49
Reply from 205.171.3.25: bytes=32 time=6ms TTL=49

Ping statistics for 205.171.3.25:
Packets: Sent = 47, Received = 41, Lost = 6 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 6ms, Average = 5ms
 
This is from the iPhone + WiFi

PING 205.171.3.25 (205.171.3.25): 56 data bytes
64 bytes from 205.171.3.25: icmp_seq=0 ttl=53 time=25.305 ms
64 bytes from 205.171.3.25: icmp_seq=1 ttl=53 time=25.033 ms
64 bytes from 205.171.3.25: icmp_seq=2 ttl=53 time=23.654 ms
64 bytes from 205.171.3.25: icmp_seq=3 ttl=53 time=24.273 ms
64 bytes from 205.171.3.25: icmp_seq=4 ttl=53 time=26.560 ms
64 bytes from 205.171.3.25: icmp_seq=5 ttl=53 time=23.917 ms
64 bytes from 205.171.3.25: icmp_seq=6 ttl=53 time=24.274 ms
64 bytes from 205.171.3.25: icmp_seq=7 ttl=53 time=23.489 ms
64 bytes from 205.171.3.25: icmp_seq=8 ttl=53 time=25.603 ms

--- 205.171.3.25 ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.489/24.679/26.560/0.959 ms

PING 205.171.2.25 (205.171.2.25): 56 data bytes
64 bytes from 205.171.2.25: icmp_seq=0 ttl=53 time=21.149 ms
64 bytes from 205.171.2.25: icmp_seq=1 ttl=53 time=24.447 ms
64 bytes from 205.171.2.25: icmp_seq=2 ttl=53 time=31.560 ms
64 bytes from 205.171.2.25: icmp_seq=3 ttl=53 time=22.939 ms
64 bytes from 205.171.2.25: icmp_seq=4 ttl=53 time=24.385 ms
64 bytes from 205.171.2.25: icmp_seq=5 ttl=53 time=25.405 ms
64 bytes from 205.171.2.25: icmp_seq=6 ttl=53 time=23.114 ms
64 bytes from 205.171.2.25: icmp_seq=7 ttl=53 time=23.863 ms

--- 205.171.2.25 ping statistics ---
9 packets transmitted, 8 packets received, 11.1% packet loss
round-trip min/avg/max/stddev = 21.149/24.608/31.560/2.885 ms
 
Very flaky hosts. Many ISP DNS servers are unreliable. use 1.1.1.1 or 8.8.8.8

[root@debian ~]# ping 205.171.2.25
PING 205.171.2.25 (205.171.2.25) 56(84) bytes of data.

--- 205.171.2.25 ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11000ms

[root@debian ~]# ping 205.171.3.25
PING 205.171.3.25 (205.171.3.25) 56(84) bytes of data.

--- 205.171.3.25 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 7999ms
 
Try this website. www.speedtest.net/ Do this from a computer as close to the provider modem. Either plug into the modem or use the router just off the modem. Hardwired connections eliminate wifi problems. You can use this site as a way of diagnosing your house internet delivery versus provider modem.
 
Originally Posted by wwillson
Very flaky hosts. Many ISP DNS servers are unreliable. use 1.1.1.1 or 8.8.8.8

[root@debian ~]# ping 205.171.2.25
PING 205.171.2.25 (205.171.2.25) 56(84) bytes of data.

--- 205.171.2.25 ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11000ms

[root@debian ~]# ping 205.171.3.25
PING 205.171.3.25 (205.171.3.25) 56(84) bytes of data.

--- 205.171.3.25 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 7999ms


Yup, they are, in many cases one of the "major" providers like CF or Cisco is also significantly faster. Not sure I trust Google doing my DNS lookup, lol.
 
Originally Posted by ZeeOSix
Originally Posted by OVERKILL
You should run DNS Bench against it, LOL!!!

https://www.grc.com/dns/benchmark.htm


Did you run it? I'm betting it doesn't look good. I can't believe the CenturyLink tech I was live chatting with didn't find anything wrong when he pinged those DNS servers.


No, it usually only makes sense to do it from the host that's using them. There would be a ton of hops for me doing it from Canada, so not representative of the performance you'd see.
 
Back
Top