Funny Telkom DNS results using Check DNS Response Time/ DNS Speed Test

[bekdik]

I tested DNS response using a couple of tools, inter alia http://network-speed.com/dnstime.php

I tested the response of pinging ping.telkomsa.net against Google's DNS server at 8.8.8.8, and Telkom's DNS servers at 196.43.46.190 and 196.43.34.190 .

This doesn't look right to me, maybe a more knowledgeable formite can comment.

Sending queries to DNS Server 8.8.8.8 (google-public-dns-a.google.com)

Query no : 1 - ping.telnetsa.net DNS response time : 0.2922 seconds
Query no : 2 - ping.telnetsa.net DNS response time : 0.0097 seconds
Query no : 3 - ping.telnetsa.net DNS response time : 0.0091 seconds
Query no : 4 - ping.telnetsa.net DNS response time : 0.0095 seconds
Query no : 5 - ping.telnetsa.net DNS response time : 0.0092 seconds
Query no : 6 - ping.telnetsa.net DNS response time : 0.0104 seconds
Query no : 7 - ping.telnetsa.net DNS response time : 0.0101 seconds
Query no : 8 - ping.telnetsa.net DNS response time : 0.0088 seconds
Query no : 9 - ping.telnetsa.net DNS response time : 0.0097 seconds
Query no : 10 - ping.telnetsa.net DNS response time : 0.0112 seconds

Average response time of DNS Server 8.8.8.8 is: 0.038
- See more at: http://network-speed.com/dnstime.php#sthash.ROAPUwFf.dpuf

Sending queries to DNS Server 196.43.46.190 (wblv-ip-dns.saix.net)

Query no : 1 - ping.telnetsa.net DNS response time : 0.3623 seconds
Query no : 2 - ping.telnetsa.net DNS response time : 0.3628 seconds
Query no : 3 - ping.telnetsa.net DNS response time : 0.3632 seconds
Query no : 4 - ping.telnetsa.net DNS response time : 0.3654 seconds
Query no : 5 - ping.telnetsa.net DNS response time : 0.3672 seconds
Query no : 6 - ping.telnetsa.net DNS response time : 0.3706 seconds
Query no : 7 - ping.telnetsa.net DNS response time : 0.3632 seconds
Query no : 8 - ping.telnetsa.net DNS response time : 5.3701 seconds
Query no : 9 - ping.telnetsa.net DNS response time : 0.3622 seconds
Query no : 10 - ping.telnetsa.net DNS response time : 0.3634 seconds

Average response time of DNS Server 196.43.46.190 is: 0.865
- See more at: http://network-speed.com/dnstime.php#sthash.dytqwzDb.dpuf

Sending queries to DNS Server 196.43.34.190 (wbs-ip-dns.saix.net)

Query no : 1 - ping.telnetsa.net DNS response time : 0.3512 seconds
Query no : 2 - ping.telnetsa.net DNS response time : 0.352 seconds
Query no : 3 - ping.telnetsa.net DNS response time : 0.3566 seconds
Query no : 4 - ping.telnetsa.net DNS response time : 0.3568 seconds
Query no : 5 - ping.telnetsa.net DNS response time : 0.3512 seconds
Query no : 6 - ping.telnetsa.net DNS response time : 0.3531 seconds
Query no : 7 - ping.telnetsa.net DNS response time : 0.351 seconds
Query no : 8 - ping.telnetsa.net DNS response time : 0.3509 seconds
Query no : 9 - ping.telnetsa.net DNS response time : 0.3526 seconds
Query no : 10 - ping.telnetsa.net DNS response time : 0.354 seconds

Average response time of DNS Server 196.43.34.190 is: 0.3529
- See more at: http://network-speed.com/dnstime.php#sthash.lHcHOr6O.dpuf

 

[rrh]

You can also try DNS Benchmark from GRC.com

 

[bekdik]

You can also try DNS Benchmark from GRC.com

I tried a few of these tools.

What puzzles me is the long times taken when using Telkom's DNS servers compared with using Google's DNS server.

A long dns resolution time will reflect in slow responses and hesitations in retrieving web pages and emails which have web content.

So the question is "Is it the location of the tool that's causing the slow response, or is it Telkom's servers tardy response?"

 

[Impulse_One]

Looks like it is location of that tool responsible for delay. There is no way in SA to get 9ms for google DNS (since it is located in Europe).

 

[Tinuva]

bekdik, the reason is simple.

1. You are testing from an international location. The tests are done from network-speed.com's webservers, which by the looks of it, sits in India, Chennai.

2. They probably have local google dns servers there in Chennai.

3. South Africa from Chennai will have high latency, and thus dns requests, even if cached, will take much longer to respond. Chennai servers/users shouldn't use south african dns servers. Strange, is that Telkom's DNS servers are open to users/servers in India...bad, because they can be used for dns reflection attacks.


So there you have it. You need to test from a local server, or better, an application on your pc, for true results for your location.
I suggest NameBench.

Thx.

 

[bekdik]

bekdik, the reason is simple.

1. You are testing from an international location. The tests are done from network-speed.com's webservers, which by the looks of it, sits in India, Chennai.

2. They probably have local google dns servers there in Chennai.

3. South Africa from Chennai will have high latency, and thus dns requests, even if cached, will take much longer to respond. Chennai servers/users shouldn't use south african dns servers. Strange, is that Telkom's DNS servers are open to users/servers in India...bad, because they can be used for dns reflection attacks.


So there you have it. You need to test from a local server, or better, an application on your pc, for true results for your location.
I suggest NameBench.

Thx.

Thanks.