cancel
Showing results for 
Search instead for 
Did you mean: 

Internet with modem

Highlighted
Supporting Actor Film
5 0 0

Bad connectivity to DNS servers

$ ping 62.2.24.158
PING 62.2.24.158 (62.2.24.158) 56(84) bytes of data.
64 bytes from 62.2.24.158: icmp_seq=1 ttl=58 time=15.9 ms
64 bytes from 62.2.24.158: icmp_seq=2 ttl=58 time=12.1 ms
64 bytes from 62.2.24.158: icmp_seq=4 ttl=58 time=14.1 ms
64 bytes from 62.2.24.158: icmp_seq=6 ttl=58 time=18.0 ms
64 bytes from 62.2.24.158: icmp_seq=12 ttl=58 time=16.5 ms
^C
--- 62.2.24.158 ping statistics ---
14 packets transmitted, 5 received, 64% packet loss, time 13164ms
rtt min/avg/max/mdev = 12.143/15.374/18.018/2.038 ms

 

 

$ ping 62.2.17.61
PING 62.2.17.61 (62.2.17.61) 56(84) bytes of data.
64 bytes from 62.2.17.61: icmp_seq=3 ttl=57 time=16.4 ms
64 bytes from 62.2.17.61: icmp_seq=4 ttl=57 time=14.3 ms
64 bytes from 62.2.17.61: icmp_seq=9 ttl=57 time=40.5 ms
64 bytes from 62.2.17.61: icmp_seq=15 ttl=57 time=17.4 ms
64 bytes from 62.2.17.61: icmp_seq=16 ttl=57 time=13.5 ms
64 bytes from 62.2.17.61: icmp_seq=17 ttl=57 time=14.7 ms
^C
--- 62.2.17.61 ping statistics ---
18 packets transmitted, 6 received, 66% packet loss, time 17242ms
rtt min/avg/max/mdev = 13.596/19.522/40.578/9.507 ms

 

 

$ ping 62.2.24.162
PING 62.2.24.162 (62.2.24.162) 56(84) bytes of data.
64 bytes from 62.2.24.162: icmp_seq=2 ttl=57 time=15.4 ms
64 bytes from 62.2.24.162: icmp_seq=3 ttl=57 time=12.7 ms
64 bytes from 62.2.24.162: icmp_seq=4 ttl=57 time=13.8 ms
64 bytes from 62.2.24.162: icmp_seq=8 ttl=57 time=16.9 ms
64 bytes from 62.2.24.162: icmp_seq=10 ttl=57 time=13.0 ms
64 bytes from 62.2.24.162: icmp_seq=13 ttl=57 time=18.7 ms
64 bytes from 62.2.24.162: icmp_seq=14 ttl=57 time=13.7 ms
64 bytes from 62.2.24.162: icmp_seq=15 ttl=57 time=12.6 ms
64 bytes from 62.2.24.162: icmp_seq=16 ttl=57 time=15.0 ms
^C
--- 62.2.24.162 ping statistics ---
16 packets transmitted, 9 received, 43% packet loss, time 15155ms
rtt min/avg/max/mdev = 12.625/14.675/18.711/1.948 ms

 

$ ping 62.2.17.60
PING 62.2.17.60 (62.2.17.60) 56(84) bytes of data.
64 bytes from 62.2.17.60: icmp_seq=1 ttl=58 time=64.9 ms
64 bytes from 62.2.17.60: icmp_seq=2 ttl=58 time=23.7 ms
64 bytes from 62.2.17.60: icmp_seq=3 ttl=58 time=12.4 ms
64 bytes from 62.2.17.60: icmp_seq=7 ttl=58 time=12.9 ms
64 bytes from 62.2.17.60: icmp_seq=8 ttl=58 time=17.5 ms
64 bytes from 62.2.17.60: icmp_seq=11 ttl=58 time=14.8 ms
64 bytes from 62.2.17.60: icmp_seq=13 ttl=58 time=12.6 ms
64 bytes from 62.2.17.60: icmp_seq=14 ttl=58 time=12.6 ms
64 bytes from 62.2.17.60: icmp_seq=15 ttl=58 time=13.9 ms
^C
--- 62.2.17.60 ping statistics ---
15 packets transmitted, 9 received, 40% packet loss, time 14126ms
rtt min/avg/max/mdev = 12.491/20.634/64.964/16.047 ms

 

1 REPLY 1
Highlighted
TV Actor
34 22 1

Re: Bad connectivity to DNS servers

Hi ykraynov,

Hope this finds you and your loved ones well, I saw that yesterday evening from 18:30, when I started to have my work VPN loose connection, so I just updated my router to have both UPC Cablecom DNS and Google, from then onwards my house connection was stable and everyone could could watch Netflix and I could continue working.

Hope it’s helpful and wish you a lovely day.

Ahmed