On Wednesday 29 August 2007 01:38, Siddhesh Poyarekar wrote:
I think the issue is more of routing to google.com than DNS. I've been using OpenDNS for a few days now and the difference between Sify and MTNL when it comes to loading google.com is still immense with Sify being the better of the two.
That would be the upstream bandwidth bottleneck - VSNL waht does traceroute on sify say?.
Too bad we can't have Open routing as well :)
U have open routing protocols. But u dont have an open wire. U have wireless but that wont solve the bandwidth problem.
On 8/29/07, jtd jtd@mtnl.net.in wrote:
That would be the upstream bandwidth bottleneck - VSNL waht does traceroute on sify say?.
Yes, the bottleneck is at VSNL for MTNL. Here's how Sify goes...
3 210.18.25.1.sify.net (210.18.25.1) 2.534 ms 5.922 ms 7.652 ms 4 210.18.25.18.sify.net (210.18.25.18) 4.361 ms 5.395 ms 5.681 ms 5 lan-202-144-83-9.maa.sify.net (202.144.83.9) 7.932 ms 10.792 ms 8.113 ms 6 * 210-210-4-96.lan.sify.net (210.210.4.96) 6.595 ms 11.955 ms 7 210.18.5.130.sify.net (210.18.5.130) 6.175 ms 8.480 ms 15.615 ms 8 lan-202-144-113-151.maa.sify.net (202.144.113.151) 8.719 ms 7.761 ms 8.449 ms 9 72.14.196.97 (72.14.196.97) 10.730 ms 9.690 ms 10.960 ms 10 * 216.239.43.214 (216.239.43.214) 11.014 ms 17.116 ms 11 216.239.43.207 (216.239.43.207) 163.567 ms 167.204 ms * 12 216.239.47.233 (216.239.47.233) 179.152 ms 169.596 ms 216.239.47.235 (216.239.47.235) 164.059 ms 13 * 209.85.248.131 (209.85.248.131) 248.581 ms 248.473 ms 14 72.14.233.117 (72.14.233.117) 294.845 ms 297.787 ms 72.14.233.55 (72.14.233.55) 246.819 ms 15 64.233.175.210 (64.233.175.210) 299.417 ms 66.249.95.247 (66.249.95.247) 296.235 ms 299.214 ms 16 72.14.232.53 (72.14.232.53) 300.296 ms 302.074 ms 294.349 ms 17 72.14.232.70 (72.14.232.70) 302.213 ms 295.260 ms 64.233.175.26 (64.233.175.26) 306.208 ms 18 py-in-f99.google.com (64.233.167.99) 299.323 ms * 295.046 ms
-
jtd -
Siddhesh Poyarekar