lightgreen49
Regular
ok MTNL delhi user we all have told to use DNS (Primary) 59.179.243.70 and Alternate DNS (Secondary) : 203.94.243.70 for it .. now i tried to check the speed not by some tool but by simple cmd cammands .
though people suggest using google DNS (8.8.8.8) and 8.8.8.4(often dead on mtnl net ) .
if u try pinging them both seperately u will see that both take equal time
C:>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=10ms TTL=54
Reply from 8.8.8.8: bytes=32 time=12ms TTL=54
Reply from 8.8.8.8: bytes=32 time=11ms TTL=54
Reply from 8.8.8.8: bytes=32 time=11ms TTL=54
======================================
C:>ping 8.8.8.4
Pinging 8.8.8.4 with 32 bytes of data:
Request timed out.
Request timed out.
=====================================
C:>ping 59.179.243.70
Pinging 59.179.243.70 with 32 bytes of data:
Reply from 59.179.243.70: bytes=32 time=10ms TTL=247
Reply from 59.179.243.70: bytes=32 time=11ms TTL=247
Reply from 59.179.243.70: bytes=32 time=9ms TTL=247
Reply from 59.179.243.70: bytes=32 time=9ms TTL=247
=====================================
C:>ping 203.94.243.70
Pinging 203.94.243.70 with 32 bytes of data:
Reply from 203.94.243.70: bytes=32 time=9ms TTL=248
Reply from 203.94.243.70: bytes=32 time=10ms TTL=248
Reply from 203.94.243.70: bytes=32 time=10ms TTL=248
Reply from 203.94.243.70: bytes=32 time=10ms TTL=248
=========================================
and if u try tracert them
Tracing route to triband-del-59.179.243.70.bol.net.in [59.179.243.70]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 10 ms 11 ms triband-del-
4 10 ms 10 ms 10 ms triband-del-
5 10 ms 9 ms 10 ms
6 12 ms 11 ms 10 ms
7 10 ms 11 ms 10 ms triband-del-59.179.243.70.bol.net.in [59.179.243.70]
=====================================================
Tracing route to ns2.mtnl.net.in [203.94.243.70]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 10 ms triband-del-
4 10 ms 10 ms 10 ms triband-del-
5 9 ms 10 ms 10 ms
6 11 ms 11 ms 10 ms ns2.mtnl.net.in [203.94.243.70]
=====================================================
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 10 ms 10 ms triband-del-
4 13 ms 11 ms 10 ms triband-del-
5 14 ms 13 ms 14 ms 221-135-69-241.sify.net [221.135.69.241]
6 12 ms 13 ms 11 ms 221-134-189-189.sify.net [221.134.189.189]
7 11 ms 10 ms 11 ms 72.14.215.37
8 11 ms 11 ms 11 ms 72.14.237.3
9 12 ms 11 ms 11 ms google-public-dns-a.google.com [8.8.8.8]
=======================================================
based on above result one can see that it will definetely take lesser amount of time for MTNL DNS to response rather then of google dns which take like a visit USA of packets .. and if u consider a webpage there are numerous facebook and scripts which ask for such dns address .. so will it not be optimam to use mtnl DELHI DNS server itself ?
though people suggest using google DNS (8.8.8.8) and 8.8.8.4(often dead on mtnl net ) .
if u try pinging them both seperately u will see that both take equal time
C:>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=10ms TTL=54
Reply from 8.8.8.8: bytes=32 time=12ms TTL=54
Reply from 8.8.8.8: bytes=32 time=11ms TTL=54
Reply from 8.8.8.8: bytes=32 time=11ms TTL=54
======================================
C:>ping 8.8.8.4
Pinging 8.8.8.4 with 32 bytes of data:
Request timed out.
Request timed out.
=====================================
C:>ping 59.179.243.70
Pinging 59.179.243.70 with 32 bytes of data:
Reply from 59.179.243.70: bytes=32 time=10ms TTL=247
Reply from 59.179.243.70: bytes=32 time=11ms TTL=247
Reply from 59.179.243.70: bytes=32 time=9ms TTL=247
Reply from 59.179.243.70: bytes=32 time=9ms TTL=247
=====================================
C:>ping 203.94.243.70
Pinging 203.94.243.70 with 32 bytes of data:
Reply from 203.94.243.70: bytes=32 time=9ms TTL=248
Reply from 203.94.243.70: bytes=32 time=10ms TTL=248
Reply from 203.94.243.70: bytes=32 time=10ms TTL=248
Reply from 203.94.243.70: bytes=32 time=10ms TTL=248
=========================================
and if u try tracert them
Tracing route to triband-del-59.179.243.70.bol.net.in [59.179.243.70]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 10 ms 11 ms triband-del-
4 10 ms 10 ms 10 ms triband-del-
5 10 ms 9 ms 10 ms
6 12 ms 11 ms 10 ms
7 10 ms 11 ms 10 ms triband-del-59.179.243.70.bol.net.in [59.179.243.70]
=====================================================
Tracing route to ns2.mtnl.net.in [203.94.243.70]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 10 ms triband-del-
4 10 ms 10 ms 10 ms triband-del-
5 9 ms 10 ms 10 ms
6 11 ms 11 ms 10 ms ns2.mtnl.net.in [203.94.243.70]
=====================================================
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 10 ms 10 ms triband-del-
4 13 ms 11 ms 10 ms triband-del-
5 14 ms 13 ms 14 ms 221-135-69-241.sify.net [221.135.69.241]
6 12 ms 13 ms 11 ms 221-134-189-189.sify.net [221.134.189.189]
7 11 ms 10 ms 11 ms 72.14.215.37
8 11 ms 11 ms 11 ms 72.14.237.3
9 12 ms 11 ms 11 ms google-public-dns-a.google.com [8.8.8.8]
=======================================================
based on above result one can see that it will definetely take lesser amount of time for MTNL DNS to response rather then of google dns which take like a visit USA of packets .. and if u consider a webpage there are numerous facebook and scripts which ask for such dns address .. so will it not be optimam to use mtnl DELHI DNS server itself ?