Following is a traceroute with the DNS ADV DNS'esTracing route to google.com [74.125.228.72] over a maximum of 30 hops: 1 2 ms 4 ms 2 ms 192.168.0.1 2 * * * Request timed out. 3 10 ms 13 ms 11 ms 117.194.64.1 4 12 ms 11 ms 11 ms 218.248.162.70 5 180 ms 177 ms 177 ms 218.248.255.54 6 265 ms 263 ms 266 ms 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149] 7 340 ms 341 ms 341 ms 121.240.1.50 8 266 ms 267 ms 265 ms 72.14.233.204 9 300 ms 295 ms 297 ms 66.249.94.74 10 554 ms 553 ms 559 ms 66.249.94.104 11 362 ms 365 ms 365 ms 64.233.175.1 12 586 ms 586 ms 587 ms 209.85.255.58 13 462 ms 460 ms 461 ms 64.233.174.178 14 514 ms 515 ms 515 ms 72.14.239.80 15 521 ms 519 ms 521 ms 72.14.239.65 16 751 ms 825 ms 761 ms 72.14.235.11 17 529 ms 529 ms 529 ms 72.14.238.247 18 730 ms 731 ms 731 ms iad23s07-in-f8.1e100.net [74.125.228.72] (which server is this resolving to?)
BSNL Broadband Routing Issue [High Latency + Low Speeds]
- Thread starter AgentX
- Start date
- Replies 108
- Views 26,813
mgcarley
Founder, Hayai Broadband
k if u want full bandwidth just go to congestion free DNS 156.154.70.1 /156.154.71.1....
But u need to SACRIFICE for your ping/latency this gonna be horrible.....
These DNS(DNS adv) WORKS ONLY IF your CO is overloaded....
TO ALL WHO HAS SPEED PROBLEMS JUST GIVE IT A TRY. . . . . .........
Not on BSNL, but reiterating points I've made previously: using this DNS made things significantly worse for me - speeds dropped by between 50 & 80% depending on what I was doing. For example, I can't watch Youtube videos at 1080p with this DNS whereas usually no problem even at 4k.
Your mileage may vary but you're almost definitely better off with Google DNS or better yet, your ISPs DNS.
actually,isp's automatic dns is the best dns....
This is true except where ISPs DNS is slow/unstable.
DNS is sometimes responsible/may not be responsible or latency/speed.
Rarely will it affect speeds of any site EXCEPT when those sites are delivered by a CDN. Your ISP *should* know the best route to the nearest CDN node if it's not already got such a node in it's network. For example, my ISP has Akamai boxes and direct peering with Google. NOT using my ISP's DNS will result in those high-speed links being ignored and significant reductions in my experiences in using any site delivered by (in my case) Akamai or Google's network.
This is quite complex to tell Unless u know whats exactly things are in bsnl nib..
I'm not sure even BSNL knows what's going on in it's network half the time
Following is a traceroute with the DNS ADV DNS'es
Tracing route to google.com [74.125.228.72] over a maximum of 30 hops:
......
18 730 ms 731 ms 731 ms iad23s07-in-f8.1e100.net [74.125.228.72] (which server is this resolving to?)
IAD is Houston, Texas.
But u need to SACRIFICE for your ping/latency this gonna be horrible.....
These DNS(DNS adv) WORKS ONLY IF your CO is overloaded....
TO ALL WHO HAS SPEED PROBLEMS JUST GIVE IT A TRY. . . . . .........
Not on BSNL, but reiterating points I've made previously: using this DNS made things significantly worse for me - speeds dropped by between 50 & 80% depending on what I was doing. For example, I can't watch Youtube videos at 1080p with this DNS whereas usually no problem even at 4k.
Your mileage may vary but you're almost definitely better off with Google DNS or better yet, your ISPs DNS.
actually,isp's automatic dns is the best dns....
This is true except where ISPs DNS is slow/unstable.
DNS is sometimes responsible/may not be responsible or latency/speed.
Rarely will it affect speeds of any site EXCEPT when those sites are delivered by a CDN. Your ISP *should* know the best route to the nearest CDN node if it's not already got such a node in it's network. For example, my ISP has Akamai boxes and direct peering with Google. NOT using my ISP's DNS will result in those high-speed links being ignored and significant reductions in my experiences in using any site delivered by (in my case) Akamai or Google's network.
This is quite complex to tell Unless u know whats exactly things are in bsnl nib..
I'm not sure even BSNL knows what's going on in it's network half the time
Following is a traceroute with the DNS ADV DNS'es
Tracing route to google.com [74.125.228.72] over a maximum of 30 hops:
......
18 730 ms 731 ms 731 ms iad23s07-in-f8.1e100.net [74.125.228.72] (which server is this resolving to?)
IAD is Houston, Texas.
Following is a traceroute with the DNS ADV DNS'es
Tracing route to google.com [74.125.228.72] over a maximum of 30 hops:
1 2 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 13 ms 11 ms 117.194.64.1
4 12 ms 11 ms 11 ms 218.248.162.70
5 180 ms 177 ms 177 ms 218.248.255.54
6 265 ms 263 ms 266 ms 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149]
7 340 ms 341 ms 341 ms 121.240.1.50
8 266 ms 267 ms 265 ms 72.14.233.204
9 300 ms 295 ms 297 ms 66.249.94.74
10 554 ms 553 ms 559 ms 66.249.94.104
11 362 ms 365 ms 365 ms 64.233.175.1
12 586 ms 586 ms 587 ms 209.85.255.58
13 462 ms 460 ms 461 ms 64.233.174.178
14 514 ms 515 ms 515 ms 72.14.239.80
15 521 ms 519 ms 521 ms 72.14.239.65
16 751 ms 825 ms 761 ms 72.14.235.11
17 529 ms 529 ms 529 ms 72.14.238.247
18 730 ms 731 ms 731 ms iad23s07-in-f8.1e100.net [74.125.228.72] (which server is this resolving to?)
ahhhh???? i use dns advantage sometimes on ubuntu...but pings are not this bad !!!!!!!!!
din help with the speed ??? hmmm
DNS advantage has servers in india..wiki is not sure about that....
Tracing route to google.com [74.125.228.72] over a maximum of 30 hops:
1 2 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 13 ms 11 ms 117.194.64.1
4 12 ms 11 ms 11 ms 218.248.162.70
5 180 ms 177 ms 177 ms 218.248.255.54
6 265 ms 263 ms 266 ms 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149]
7 340 ms 341 ms 341 ms 121.240.1.50
8 266 ms 267 ms 265 ms 72.14.233.204
9 300 ms 295 ms 297 ms 66.249.94.74
10 554 ms 553 ms 559 ms 66.249.94.104
11 362 ms 365 ms 365 ms 64.233.175.1
12 586 ms 586 ms 587 ms 209.85.255.58
13 462 ms 460 ms 461 ms 64.233.174.178
14 514 ms 515 ms 515 ms 72.14.239.80
15 521 ms 519 ms 521 ms 72.14.239.65
16 751 ms 825 ms 761 ms 72.14.235.11
17 529 ms 529 ms 529 ms 72.14.238.247
18 730 ms 731 ms 731 ms iad23s07-in-f8.1e100.net [74.125.228.72] (which server is this resolving to?)
ahhhh???? i use dns advantage sometimes on ubuntu...but pings are not this bad !!!!!!!!!
din help with the speed ??? hmmm
DNS advantage has servers in india..wiki is not sure about that....
my isp??? you mean airtel???? or your own isp???
yes i have seen airtel giving excellent results.when i checked out its trace route to att.com on my friends home..got the output in 5 hops with 37ms~45ms
through akmai.
When i change my open dns/google dns to default dns on my bsnl here is the result....
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert AT&T Cell Phones, U-verse, Digital TV, DSL Internet, and Phone Service
Tracing route to e2318.dscb.akamaiedge.net [23.57.201.145]
over a maximum of 30 hops:
1 1 ms
yes i have seen airtel giving excellent results.when i checked out its trace route to att.com on my friends home..got the output in 5 hops with 37ms~45ms
through akmai.
When i change my open dns/google dns to default dns on my bsnl here is the result....
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert AT&T Cell Phones, U-verse, Digital TV, DSL Internet, and Phone Service
Tracing route to e2318.dscb.akamaiedge.net [23.57.201.145]
over a maximum of 30 hops:
1 1 ms
Horrible latency for the last few days during the daytime - 380-400+ ms latency to US servers, 320+ to EU. Airtel is normal as usual (310-320ms) so it's just f*cked up congested routes on BSNL's end. American traffic is being routed via flagtel (sh*tty and congested) in London, or some super messed up route going to US via paris/montreal which is even worse.No matter what gateway you get, it's garbage, congested, and causes huge latency fluctuations and packet loss. As usual this is happening mainly during the day.
Horrible latency for the last few days during the daytime - 380-400+ ms latency to US servers, 320+ to EU. Airtel is normal as usual (310-320ms) so it's just f*cked up congested routes on BSNL's end.
American traffic is being routed via flagtel (sh*tty and congested) in London, or some super messed up route going to US via paris/montreal which is even worse.
No matter what gateway you get, it's garbage, congested, and causes huge latency fluctuations and packet loss. As usual this is happening mainly during the day.
you guys have screwed up your own routes using open/google/dns adv/singtel.....etc. USE these when u need it:tranquillity (2):.
Just search for good your own isp dns serverss.just see my results:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert XFINITY by Comcast -- Official Customer Site | Email | Watch TV Online
Tracing route to a1526.dscg.akamai.net [115.112.2.21]
over a maximum of 30 hops:
1 1 ms
American traffic is being routed via flagtel (sh*tty and congested) in London, or some super messed up route going to US via paris/montreal which is even worse.
No matter what gateway you get, it's garbage, congested, and causes huge latency fluctuations and packet loss. As usual this is happening mainly during the day.
you guys have screwed up your own routes using open/google/dns adv/singtel.....etc. USE these when u need it:tranquillity (2):.
Just search for good your own isp dns serverss.just see my results:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HOME>tracert XFINITY by Comcast -- Official Customer Site | Email | Watch TV Online
Tracing route to a1526.dscg.akamai.net [115.112.2.21]
over a maximum of 30 hops:
1 1 ms
you guys have screwed up your own routes using open/google/dns adv/singtel.....etc. USE these when u need it:tranquillity (2):.
I'm sorry if you find me rude, but you absolutely have no idea what's going on here.
This is a genuine thread, about us unfortunate consumers who couldn't get their internet working the way it should be. Just because your route is good, that doesn't mean it's good because of the selection of DNS servers you utilize. It's either because of the BSNL gateway in your area is under-utilized or is properly managed or you're just being lucky, just like the way I was lucky a couple of months ago.
Talking about DNS servers, they JUST resolve the domain names to IP addresses. They have absolutely nothing to do with the latency issue being discussed here.
I'm sorry if you find me rude, but you absolutely have no idea what's going on here.
This is a genuine thread, about us unfortunate consumers who couldn't get their internet working the way it should be. Just because your route is good, that doesn't mean it's good because of the selection of DNS servers you utilize. It's either because of the BSNL gateway in your area is under-utilized or is properly managed or you're just being lucky, just like the way I was lucky a couple of months ago.
Talking about DNS servers, they JUST resolve the domain names to IP addresses. They have absolutely nothing to do with the latency issue being discussed here.
Just because your route is good, that doesn't mean it's good because of the selection of DNS servers you utilize.
As far as I know every time you connect to BSNL you are assigned a gateway, and with it a slightly different route (although the overall routing is same - same company router at each hop, but possibly a different physical server).
Changing the dns server, like you said, doesn't really have any effect on the routing at all. But disconnecting and reconnecting to BSNL using a dialer gives you a potentially fresh and uncongested gateway. This works really well during the night, when there are many "free" servers along the route. But during the day when every pathway along the route is congested, it doesn't work.
Also, the problem will almost always happen on routes **OUTSIDE** India, I always see people link tracerts/speedtest results to servers in india, but that's completely useless for the most part.
Theoretically if you get bad latency & congestion all along the route from anywhere in India, everyone in India should be experiencing issues. I'm 100% positive, almost everyone experiences network congestion particularly during the day at peak hours, at the start of the month; and the random packet loss from excessive congestion every few days.
As far as I know every time you connect to BSNL you are assigned a gateway, and with it a slightly different route (although the overall routing is same - same company router at each hop, but possibly a different physical server).
Changing the dns server, like you said, doesn't really have any effect on the routing at all. But disconnecting and reconnecting to BSNL using a dialer gives you a potentially fresh and uncongested gateway. This works really well during the night, when there are many "free" servers along the route. But during the day when every pathway along the route is congested, it doesn't work.
Also, the problem will almost always happen on routes **OUTSIDE** India, I always see people link tracerts/speedtest results to servers in india, but that's completely useless for the most part.
Theoretically if you get bad latency & congestion all along the route from anywhere in India, everyone in India should be experiencing issues. I'm 100% positive, almost everyone experiences network congestion particularly during the day at peak hours, at the start of the month; and the random packet loss from excessive congestion every few days.
dude there is an ultimate technique....it may sound lame but it ll work...first remove the lan cable, dsl cable(phone wire) nd switch off modemthen connect the lan cable properly followed by dsl cable nd switch on the modemafter doing this, the pings should be fine(always works for me 
)enjoy 
)enjoy BSNL/VSNL Routing through Johannesburg???C:\>tracert tellall.orgTracing route to tellall.org [95.211.73.193] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 192.168.0.1 2 * * * Request timed out. 3 13 ms 10 ms 9 ms 117.194.64.1 4 10 ms 11 ms 10 ms 218.248.162.70 5 9 ms 12 ms 8 ms 218.248.255.10 6 49 ms 52 ms 52 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163.207.81] 7 100 ms 79 ms 104 ms 172.31.19.146 8 * 78 ms 135 ms ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5] 9 171 ms 80 ms 201 ms if-2-1-0-3.core1.MLV-Mumbai.as6453.net [180.87.38.9] 10 123 ms 122 ms 123 ms if-1-0-0.core1.COV-Cochin.as6453.net [209.58.105.38] 11 124 ms 126 ms 124 ms if-1-0-1.core2.COV-Cochin.as6453.net [116.0.85.10] 12 2167 ms 2173 ms 2182 ms if-4-1-1-0.tcore2.JSO-Johannesburg.as6453.net [116.0.86.22] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out.The same issue is happening with Tata Photon, so I guess this issue is with VSNL itself
