16 December 2009

Google DNS vs OPENDNS





Testing on telkomspeedy ISP connection.

OPENDNS with IP's : 208.67.222.222 and 208.67.220.220

[box@speedy ~]$ ping 208.67.222.222 -c 3
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=54 time=251 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=54 time=250 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=54 time=254 ms

--- 208.67.222.222 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2257ms
rtt min/avg/max/mdev = 250.725/252.294/254.581/1.654 ms
[box@speedy ~]$

and

[box@speedy ~]$ ping 208.67.220.220 -c 3
PING 208.67.220.220 (208.67.220.220) 56(84) bytes of data.
64 bytes from 208.67.220.220: icmp_seq=1 ttl=54 time=246 ms
64 bytes from 208.67.220.220: icmp_seq=2 ttl=54 time=247 ms
64 bytes from 208.67.220.220: icmp_seq=3 ttl=54 time=244 ms

--- 208.67.220.220 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2244ms
rtt min/avg/max/mdev = 244.737/246.032/247.042/1.120 ms
[box@speedy ~]$


Google DNS with IP's : 8.8.8.8 and 8.8.4.4

[box@speedy ~]$ ping 8.8.8.8 -c 3
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=243 time=294 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=243 time=403 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=243 time=379 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2380ms
rtt min/avg/max/mdev = 294.660/359.318/403.581/46.749 ms
[box@speedy ~]$

and

[box@speedy ~]$ ping 8.8.4.4 -c 3
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=243 time=100 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=243 time=132 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=243 time=100 ms

--- 8.8.4.4 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2102ms
rtt min/avg/max/mdev = 100.148/110.889/132.028/14.950 ms
[box@speedy ~]$

how about telkomspeedy ?
eg. 203.130.196.155

[box@speedy ~]$ ping 203.130.196.155 -c 3
PING 203.130.196.155 (203.130.196.155) 56(84) bytes of data.
64 bytes from 203.130.196.155: icmp_seq=1 ttl=61 time=43.1 ms
64 bytes from 203.130.196.155: icmp_seq=2 ttl=61 time=64.3 ms
64 bytes from 203.130.196.155: icmp_seq=3 ttl=61 time=40.0 ms

--- 203.130.196.155 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2042ms
rtt min/avg/max/mdev = 40.042/49.188/64.329/10.783 ms
[box@speedy ~]$

See ?

5 comments:

ardyan said...

trus... mendingan pake yang mana mas.?

mazyayan said...

harusnya mending pake dns masing2 ISP, krn lebih deket. CMIIW

Pakdoz said...

Lokasi DNS server terdekat memang menjamin kecepatan resolve domain, tapi bagaimana dengan kestabilan?

Saya lihat beberapa DNS lokal, seperti punya Telkom dan Nawala sering delay atau bahkan tidak mau resolve ketika melakukan request.

Google DNS maupun OpenDNS memang jauh letaknya, tetapi untuk kestabilan sudah tidak diragukan lagi.
Sudah 2,5 tahun saya menggunakan OpenDNS dan benar2 sangat stabil.

Bagaimana supaya mendapatkan DNS yang cepet dan stabil? Buat local DNS server dengan menggunakan pdnsd atau BIND, yang resolvernya ke OpenDNS atau Google DNS.

Kecepatan bukan lagi 40ms tetapi 1ms!

Anonymous said...

sudah melakukan benchmark tdp semua layananan DNS? Jika sudah silahkan buat tulisan lanjutan

bayu said...

untuk layanan fitur, opendns jagonya
untuk dns google yang pake ISP telkom, akses nya lebih cepet daripada ke opendns, tapi gk ada fitur kek opendns

solusinya ?

seperti yang di bilang Pakdoz, bikin dns server/cache sendiri, resolvernya isa di gabungin punya ISP sendiri, DNS Google, ato pake Opendns.

fiturnya ? tergantung aplikasi apa yang digunakan sebagai dns server/cache lokal tersebut.

aq biasa pake dnsmasq, fitur udah mencukupi kebutuhan sehari-hari