DNS TelkomSpeedy

Berikut ini adalah beberapa DNS TelkomSpeedy yang bisa anda gunakan :

Medan         : 203.130.206.250
Batam          : 203.130.193.74
Jakarta         : 202.134.0.155
Jakarta         : 203.130.196.155
Bandung       : 222.124.204.34
Surabaya      : 202.134.1.10
Balikpapan   : 203.130.209.242
Denpasar      : 61.94.192.12

Sebelum menggunakan DNS tersebut sebaiknya lakukan ping terlebih dahulu, untuk mengetahui DNS yang tercepat.

Beberapa DNS alternative yang cepat dan stabil adalah Google Public DNS (8.8.4.4 dan 8.8.8.8). Lebih baik bila kedua DNS tersebut digabung, misalkan DNS Speedy Bandung sebagai Primary (222.124.204.34) dan DNS Google sebagai secondary (8.8.8.8).
Hasil Percobaan

Saya sudah melakukan percobaan ping ke DNS speedy dan hasilnya sebagai berikut :

203.130.193.74

PING 203.130.193.74 (203.130.193.74) 56(84) bytes of data.
64 bytes from 203.130.193.74: icmp_req=1 ttl=58 time=60.3 ms
64 bytes from 203.130.193.74: icmp_req=2 ttl=58 time=60.0 ms
64 bytes from 203.130.193.74: icmp_req=3 ttl=58 time=56.5 ms
64 bytes from 203.130.193.74: icmp_req=4 ttl=58 time=58.9 ms
64 bytes from 203.130.193.74: icmp_req=5 ttl=58 time=61.3 ms
64 bytes from 203.130.193.74: icmp_req=6 ttl=58 time=184 ms
--- 203.130.193.74 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5005ms
rtt min/avg/max/mdev = 56.569/80.371/184.980/46.806 ms

203.130.193.74

PING 203.130.193.74 (203.130.193.74) 56(84) bytes of data.
64 bytes from 203.130.193.74: icmp_req=1 ttl=58 time=60.3 ms
64 bytes from 203.130.193.74: icmp_req=2 ttl=58 time=60.0 ms
64 bytes from 203.130.193.74: icmp_req=3 ttl=58 time=56.5 ms
64 bytes from 203.130.193.74: icmp_req=4 ttl=58 time=58.9 ms
64 bytes from 203.130.193.74: icmp_req=5 ttl=58 time=61.3 ms
64 bytes from 203.130.193.74: icmp_req=6 ttl=58 time=184 ms
--- 203.130.193.74 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5005ms
rtt min/avg/max/mdev = 56.569/80.371/184.980/46.806 ms

202.134.0.155

PING 202.134.0.155 (202.134.0.155) 56(84) bytes of data.
64 bytes from 202.134.0.155: icmp_req=1 ttl=56 time=57.2 ms
64 bytes from 202.134.0.155: icmp_req=2 ttl=56 time=61.1 ms
64 bytes from 202.134.0.155: icmp_req=3 ttl=56 time=66.3 ms
64 bytes from 202.134.0.155: icmp_req=4 ttl=56 time=55.7 ms
64 bytes from 202.134.0.155: icmp_req=5 ttl=56 time=56.5 ms
64 bytes from 202.134.0.155: icmp_req=6 ttl=56 time=59.1 ms
--- 202.134.0.155 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 55.753/59.363/66.367/3.615 ms

222.124.204.34

PING 222.124.204.34 (222.124.204.34) 56(84) bytes of data.
64 bytes from 222.124.204.34: icmp_req=1 ttl=58 time=33.5 ms
64 bytes from 222.124.204.34: icmp_req=2 ttl=58 time=33.3 ms
64 bytes from 222.124.204.34: icmp_req=3 ttl=58 time=33.9 ms
64 bytes from 222.124.204.34: icmp_req=4 ttl=58 time=34.5 ms
64 bytes from 222.124.204.34: icmp_req=5 ttl=58 time=125 ms
64 bytes from 222.124.204.34: icmp_req=6 ttl=58 time=31.8 ms
--- 222.124.204.34 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 31.890/48.813/125.590/34.345 ms

blog.karo.or.id