On May 21, 2012 3:19 AM, "Mick" <[email protected]> wrote: > > On Saturday 19 May 2012 13:09:45 Pandu Poluan wrote: > > On May 19, 2012 6:46 PM, "Dale" <[email protected]> wrote: > > > Willie Matthews wrote: > > [le snip] > > > > > > You should really try changing you DNS server to some faster ones. * I* > > > > was having this same problem with my ISP or DSL modem with built in > > > > router taking a long time. I changed my DNS servers to Google DNS > > > > Servers (8.8.4.4 and 8.8.8.8) and haven't had a problem. > > > > > > > > My setup is a little different but all in all I would really suggest > > > > you try a DNS server outside of your ISP. > > > > > > I agree. My ISP is AT&T and I changed my DNS to Google's too. It is > > > very fast compared to AT&T's servers. I have had AT&T's servers not > > > respond for several seconds but Google's just seem to work. > > > > Here's the result of a test comparing the performance of public DNS servers > > > > > > http://www.thousandeyes.com/blog/public-dns-resolver-showdown > > > > Despite what the linked article said, in my experience, Level 3 > > (4.2.2.[1-5]) is at least as fast as Google. I guess it depends on one's > > ISP. But both of them are mucho faster (and much stabler) than my ISP's DNS > > servers. > > I understand that Level 3 4.2.2.2 is not a public DNS server: > > http://www.tummy.com/Community/Articles/famous-dns-server/ >
Indeed. > > If my recent experience is correct (when I was trying to set up proxychains) > connections to it are often dropped or at least throttled. > Most likely overloaded. I myself use 4.2.2.[3-5]. BTW, thanks for that link. I never knew before that http://18.62.0.96/ is a standard connectivity test ;-) Rgds,
