| 1 |
On May 19, 2012 6:46 PM, "Dale" <rdalek1967@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Willie Matthews wrote: |
| 4 |
> > |
| 5 |
|
| 6 |
[le snip] |
| 7 |
|
| 8 |
> > |
| 9 |
> > You should really try changing you DNS server to some faster ones. I was |
| 10 |
> > having this same problem with my ISP or DSL modem with built in router |
| 11 |
> > taking a long time. I changed my DNS servers to Google DNS Servers |
| 12 |
> > (8.8.4.4 and 8.8.8.8) and haven't had a problem. |
| 13 |
> > |
| 14 |
> > My setup is a little different but all in all I would really suggest you |
| 15 |
> > try a DNS server outside of your ISP. |
| 16 |
> > |
| 17 |
> |
| 18 |
> |
| 19 |
> I agree. My ISP is AT&T and I changed my DNS to Google's too. It is |
| 20 |
> very fast compared to AT&T's servers. I have had AT&T's servers not |
| 21 |
> respond for several seconds but Google's just seem to work. |
| 22 |
> |
| 23 |
|
| 24 |
Here's the result of a test comparing the performance of public DNS servers |
| 25 |
: |
| 26 |
|
| 27 |
http://www.thousandeyes.com/blog/public-dns-resolver-showdown |
| 28 |
|
| 29 |
Despite what the linked article said, in my experience, Level 3 |
| 30 |
(4.2.2.[1-5]) is at least as fast as Google. I guess it depends on one's |
| 31 |
ISP. But both of them are mucho faster (and much stabler) than my ISP's DNS |
| 32 |
servers. |
| 33 |
|
| 34 |
But stay away from OpenDNS like the plague. They are known to perform false |
| 35 |
resolve, especially if the domain being resolved does not exist. |
| 36 |
|
| 37 |
Best of all would be to create a list of public DNS servers, and feed it |
| 38 |
into a DNS Benchmarking tool, such as this one from GRC: |
| 39 |
|
| 40 |
http://www.grc.com/dns/benchmark.htm |
| 41 |
|
| 42 |
The above tool is how I determine Level 3 to be on a par with Google. |
| 43 |
(Sorry, the GRC Tool is Windows-only, but within the article there's an |
| 44 |
explanation on how the tool works, so it should be emulatable using bash |
| 45 |
and dig). |
| 46 |
|
| 47 |
Rgds, |
Archives