Best DNS server using "Namebench" to determine. Results included.

M

MegasXLR

Banned
Joined
Nov 17, 2010
Messages
1,965
Reaction score
3
Out of desperation a while ago I started using Google as DNS server for my Netgear DG834GT ADSL router/modem. It was OK but then I stumbled upon this program called "Namebench.exe" doing research when I had some issues with DNS again. I found that for South Africa Google is still to slow for obvious reasons so I ran the program and determined the "best" servers. That was two weeks ago. Since then my Internet experience was much better. I ran this program again today and here is the results. Interesting, I am sure someone with more expertise can comment and advise best DNS setups based on this information

http://namebench.appspot.com/id/4837001

As my DG834 GT with custom DGTeam firmware I can set a few servers as backup. ;)
 
Pleasure is mine. Enjoy.

For anyone that did not see the other post here is a repeat.

TonyA said:
How do you go about changing the DNS setting on router. I'm tired of having to constantly reboot my router due to the same problem?
Click to expand...

in the router somewhere under DNS settings you change the option from "Auto from ISP" to "Use these addresses" the type in a primary DNS as 8.8.8.8 and secondary to 8.8.4.4.

I use these as I used an program called "Namebench" and it determined the fastest local DNS servers for me. Google was to slow. These are the recommended DNS servers.

NameBench tests

Recommended configuration (fastest + nearest)
Primary Server
196.207.36.251
Vodacom psi ZA
Secondary Server
196.28.75.200
SYS-196.28.75.200
Tertiary Server
196.43.53.190
SAIX Durban ZA

A backup DNS server for this system
Replica of SAIX Pretoria ZA-2 [196.43.50.190]

196.207.36.251 Vodacom psi ZA dnscache1-psi.3g.vodacom.co.za 196.72 22.9% 24.6

In my Netgear DG834GT with custom DGteam firmware I can set many more DNS servers as backup. So I never seem to have problems lately.
Click to expand...
 
Last edited:
For obvious reasons, your own isp's dns servers will usually be the fastest.

What most people don't know or realize is, if the adsl router shares the internet for you at home, most pcs will use the adsl modem as their DNS server, even worse is, that most adsl router's dns server are actual total rubbish. 1st, these modems do not have all that much memory, so they don't really cache anything, but they do make it slower for the internal pcs as it is a extra middleman. 2nd these modems run fairly slow cpus, so they are just slow to begin with for anything not network related (forwarding happens in hardware) that happens in software.

If you have found what is the fastest dns server for you, rather set it up on pc you use on the internet, that way you will get the most benefit from it.
 
This has just been demonstrated to me with Cybersmart.

Completely borked with anything other than its own preferred DNS servers... whereas Afrihost it does not matter.

I live and I learn... just why does it have to be so technical!

Tinuva said:
For obvious reasons, your own isp's dns servers will usually be the fastest.

What most people don't know or realize is, if the adsl router shares the internet for you at home, most pcs will use the adsl modem as their DNS server, even worse is, that most adsl router's dns server are actual total rubbish. 1st, these modems do not have all that much memory, so they don't really cache anything, but they do make it slower for the internal pcs as it is a extra middleman. 2nd these modems run fairly slow cpus, so they are just slow to begin with for anything not network related (forwarding happens in hardware) that happens in software.

If you have found what is the fastest dns server for you, rather set it up on pc you use on the internet, that way you will get the most benefit from it.
Click to expand...
 
Tinuva could you please spell out in a bit more detail how to set up PC or router to obtain fastes DNS resolution. My MWEB home page keeps cutting out and then I have to reboot router to get it working, so I think it has something to do with the DNS resolution which is set to auto on router and PC. Router is a billion 7402G and PC is running win 7 home premium. Thanks
 
Thanks, this is actually very useful. I have always played a subjective guessing game to pick DNS servers.
 
I found Namebench very erratic. I don't know if it was due to Mweb's problems recently. I would get MTNza as the fastest one time then another UltraDNS and another my own ISP. I should probably try again though.
 
PseudZ said:
I found Namebench very erratic. I don't know if it was due to Mweb's problems recently. I would get MTNza as the fastest one time then another UltraDNS and another my own ISP. I should probably try again though.
Click to expand...

Therefore you should do a few tests and select the most stable and repeatable DNS in the primary and secondary. In my case I have a tertiary DNS and more.
 
PseudZ said:
I found Namebench very erratic. I don't know if it was due to Mweb's problems recently. I would get MTNza as the fastest one time then another UltraDNS and another my own ISP. I should probably try again though.
Click to expand...

From the Faq section:

Why do I get different results each time I run namebench?

The first run is the one that is most likely to be accurate. The more times to run namebench, the more likely you are to be repeating the same queries over and over again. This will skew your results toward the closest nameserver to you, rather than the one most likely to have your requests cached during normal operations.

One work-around to avoid this is to switch between the Alexa dataset and your favorite browser as a history source. As the Alexa dataset is global in scope, it will tend to skew toward nameservers that cache queries from around the world, however.
Click to expand...
 
latro said:
From the Faq section:
Click to expand...

Why do I get different results each time I run namebench?

The first run is the one that is most likely to be accurate. The more times to run namebench, the more likely you are to be repeating the same queries over and over again. This will skew your results toward the closest nameserver to you, rather than the one most likely to have your requests cached during normal operations.

One work-around to avoid this is to switch between the Alexa dataset and your favorite browser as a history source. As the Alexa dataset is global in scope, it will tend to skew toward nameservers that cache queries from around the world, however.
Click to expand...

Ah thank you. I should read a bit more haha
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X