test dns servers

  • Thread starter Thread starter oXide
  • Start date Start date
O

oXide

hello

i have a list of 58 DNS Servers

is there any software that analyze/test DNS servers and show me what
server is faster for my conexion?


thank u :)
 
Ping.
Click to expand...
That would tell you which DNS server has the best connection to your
location but does not tell you which server actually performs the best to
your request.

ex. A heavily used DNS server would actually have a slower response to
your request then a lightly used DNS server.

Regards

Wayne D
 
hello

i have a list of 58 DNS Servers

is there any software that analyze/test DNS servers and show me what
server is faster for my conexion?
Click to expand...

http://www.xuebrothers.net/misc/dnspeed.htm

Found it from Henk's "Links to freeware".

It can only test one at a time, but it does provide a REAL test of the
DNS, and enables you to rule out those which reject you.

You may find that swapping the normal order of your own ISP's primary
and secondary works quite well.
 
http://www.xuebrothers.net/misc/dnspeed.htm

Keep in mind that a DNS server caches all looked-up entries. The first time
it gets a request for a target that it does not recognize, it must pass the
request on to a higher-level DNS server ... and then it caches the response.
So the first lookup may be slow. Subsequent lookups of the same target will
be quicker.

What these tools WON'T tell you is ... just how big is the cache? When the
cache gets full, older entries must be deleted.

So you might find two DNS servers that respond about equally fast. But you
still don't know how long it is able to retain its cached entries.

Of course, even with an infinite cache, old entries must be purged. There's
a timeout on each entry, because there's a possibility that the target's
owner will change the IP address, which would invalidate the cached entries
in all DNS servers.

Many of us have DNS servers right on our desktops (or in our closets)! That
DSL modem/router or cable modem/router may have a DNS server built in.

If so, it will cache DNS responses. But it's memory is likely quite small
compared to the big-boy DNS servers on the net. But, in your home or small
office, the number of unique target requests is small, so the router's small
cache is likely NOT a serious limitation. The benefit of having an on-site
DNS server is that you can hit that DNS (= your local router) in just a few
milliseconds, because the latency on your local network is quite small.

Compare that to the 100 or 200 millisecond latency to a DNS server provided
by your ISP (or any other DNS provider on the net).

So, if you use these DNS testing tools, don't forget to test your local DNS
server (if you have one). More than likely, the local DNS is your best
choice.
 
That would tell you which DNS server has the best connection to your
location but does not tell you which server actually performs the best to
your request.

ex. A heavily used DNS server would actually have a slower response to
your request then a lightly used DNS server.
Click to expand...
TRy reading about the switches you can use with the ping command.
 
TRy reading about the switches you can use with the ping command.
Click to expand...

Yes, but I do not believe this command " -a " does not measure the amount
of time that it takes to resolve the address. The time it shows is the
normal ping time. If you have an article that shows otherwise, please
point me to it.

Regards

Wayne D
 
Keep in mind that a DNS server caches all looked-up entries. The first time
it gets a request for a target that it does not recognize, it must pass the
request on to a higher-level DNS server ... and then it caches the response.
So the first lookup may be slow. Subsequent lookups of the same target will
be quicker.

What these tools WON'T tell you is ... just how big is the cache? When the
cache gets full, older entries must be deleted.

So you might find two DNS servers that respond about equally fast. But you
still don't know how long it is able to retain its cached entries.

Of course, even with an infinite cache, old entries must be purged. There's
a timeout on each entry, because there's a possibility that the target's
owner will change the IP address, which would invalidate the cached entries
in all DNS servers.

Many of us have DNS servers right on our desktops (or in our closets)! That
DSL modem/router or cable modem/router may have a DNS server built in.

If so, it will cache DNS responses. But it's memory is likely quite small
compared to the big-boy DNS servers on the net. But, in your home or small
office, the number of unique target requests is small, so the router's small
cache is likely NOT a serious limitation. The benefit of having an on-site
DNS server is that you can hit that DNS (= your local router) in just a few
milliseconds, because the latency on your local network is quite small.

Compare that to the 100 or 200 millisecond latency to a DNS server provided
by your ISP (or any other DNS provider on the net).

So, if you use these DNS testing tools, don't forget to test your local DNS
server (if you have one). More than likely, the local DNS is your best
choice.
Click to expand...
Very nice explanation!! Well Done.

By this explanation, it can be seen that the best solution to achieve the
fastest response would be to have a local DNS server.

A DNS catching program that you may want to try.

FastCache v1.01 179k

"As long as there's an Internet, everyone is going to want to do things
faster. Browse the web, ping servers, download files, whatever. Every
time you go to a new website, or a website you haven't been to in a day
or so, your computer needs to locate the server again using DNS. Each DNS
request can take anywhere from 50 milliseconds, to even a second or more,
but most are in the 100 to 200 millisecond range. Want to save a couple
hundred milliseconds? Probably not, but what about a couple million or
more? That's what AnalogX FastCache is all about.
AnalogX FastCache is a caching DNS server that runs on your local
machine and handles any DNS request that your computer makes, from
Internet Explorer to your favorite FTP client. Once a query is made,
FastCache will override the normal timeout for the item with one that you
specify, so instead of saving a query for a couple of seconds, it can
save it for a couple of days. Now every time you ask for it again while
it's in the cache, it gives it to you instantly. You can read more about
DNS, and how to configure your machine to run FastCache in this article
at WebAttack."

http://www.analogx.com/contents/download/network/fc.htm

Regards

Wayne D
 
Back
Top