Tip Jar: Live Dangerously! Fix your crawling BSNL DNS

Disclaimer: Implementing this change requires understanding Windows Networking. It may contravene BSNL policy.

This writer uses India’s BSNL (Bharat Sanchar Nigam Limited – what a mouthful hence the acronym) Dataone broadband service. Which is a bit of step-child with mostly outdated (and therefore useless) configuration information on the vendor’s site. That is assuming you can find said information in the first place. I usually use Google to search for DNS status updates. There’s an active thread at the India Broadband Forum where users post their experiences.

I got plumb tired of waiting for ages to open any website outside India. Including this blog. So I did a bit of digging and decided to live dangerously. I changed my DNS settings to use Google Public DNS instead.

To do so I first opened a command line window and ran ‘ipconfig /all’ to detect the existing BSNL DNS which I then carefully wrote down (in case living dangerously meant no connection). I next opened the Windows Control Panel network option and changed the primary and secondary DNS to those offered by Google for both dial-up modem IP4 DNS settings. As well as those for the LAN Card’s IP4 settings. You have to do it in both or there will be no appreciable enhancement. BSNL Router users too can change their settings by opening http://192.168.1.1 and using admin / admin as the login / password combination. If that doesn’t work check the router documentation (you did save it safe somewhere didn’t you?).

And once you are done run Ping Test (requires Flash & Java VM) to check your grade. I tried the service before changing the connection and the site timed out before it could test anything!

Broadband throughput using Mozilla Firefox 3.6.9
Broadband throughput with Mozilla Firefox 3.6.9
Broadband throughput using Google Chrome 6.0.472.x
Broadband throughput with Google Chrome 6.0.472.x

After switching to the Google DNS, I got a B grade connecting to a Mumbai (aka Bombay, India) server and a D grade connecting to Ashburn, VA (USA) servers. Do note these aren’t subjective tests because testing using a different service, Speedtest, of the same servers got completely different times! I tested with Firefox 3.6.9 and Google Chrome 6.0.472.x and Chrome was way faster!!! My poor scores may have something to do with the ancient (4+ years old) modem provided when the maximum BSNL network speed was an awe-inspiring 256 kbps!

And even if you aren’t in India, the Google Public DNS may improve your browsing speed, So why not try it. Living on the edge can be fun!

5 Comments

link says:

ok how is this supposedto mean?

emusingly says:

The post is specific to users of the Indian Dataone broadband service. If you connect using Dataone then making the changes will really speed up your connect as the default DNS is terrible. If you don’t use the service then the post can be easily skipped.

link says:

ok how is this supposedto mean?

emusingly says:

The post is specific to users of the Indian Dataone broadband service. If you connect using Dataone then making the changes will really speed up your connect as the default DNS is terrible. If you don’t use the service then the post can be easily skipped.

emusingly says:

This post is only for Indian users who connect through BSNL’s Dataone service. Whose DNS is terrible. If you aren’t in India or don’t use Dataone then the post can be easily skipped.

Comments are closed.
%d bloggers like this: