MacResource
Fix: how I got rid of massive latency by changing the DNS settings - Printable Version

+- MacResource (https://forums.macresource.com)
+-- Forum: My Category (https://forums.macresource.com/forumdisplay.php?fid=1)
+--- Forum: Tips and Deals (https://forums.macresource.com/forumdisplay.php?fid=3)
+--- Thread: Fix: how I got rid of massive latency by changing the DNS settings (/showthread.php?tid=44362)

Pages: 1 2


Fix: how I got rid of massive latency by changing the DNS settings - tuqqer - 11-29-2007

Networks, routers, Internet connections confuse the hell out of me. All I want is speed, and more of it. But for the past few months, I've seen bad latency/pause issues with my Internet connection. I'd go to some sites, and there'd be 0 up/down action for 8 to 15 seconds before the page would load. Same with ftp'ing onto my sites. It was intermittent, as some sites would load fast, but it was driving me nuts.

Finally found a guy on CraigsList who came by a couple days ago and after mucking about for a bit, found that the Buffalo routers I have use their own internal DNS by default (I've no idea if this is the norm or not). In otherwords, my Mac would use the Buffalo's DNS as the way out, and then the Buffalo router would then pass everything on to the DNS of my internet service provider (Comcast in this case). By changing the DNS numbers directly to Comcast's (and not using the internal one of the Buffalo router), the delay completely disappeared. Speeds are now freakishly fast. I mean *zero* pause. I can load 20 sites in tabs at one time, and they all load in just a few seconds, where before, it would take more than a minute.

Just info to store away in case you ever have latency issues.


Re: Fix: how I got rid of massive latency by changing the DNS settings - AAA - 11-29-2007

I followed suggestions from other folks and use 4.2.2.2 and 4.2.2.3 as DNS.
Does anyone know of any speedtesting/results on various public DNS servers?


Re: Fix: how I got rid of massive latency by changing the DNS settings - Stavs - 11-29-2007

Why thise numbers> I used open DNS based on what someone here recommended.


Re: Fix: how I got rid of massive latency by changing the DNS settings - Panopticon - 11-29-2007

By changing the DNS numbers directly to Comcast's (and not using the internal one of the Buffalo router)

Buffalo's software normally gets its DNS settings from the ISP automatically. Most routers do this.

btw, Comcast is notorious for having DN Servers go wonky without warning. When it happens, nothing will load. Thus the recommendations to use "4.2.2.2 and 4.2.2.3" or other open servers. When I used Comcrap, I set my router to use Verizons DNS. Cured the the wonkies.


Re: Fix: how I got rid of massive latency by changing the DNS settings - IronMac - 11-29-2007

I use Open DSN also...should I try the 4.2.2.2 numbers?


Re: Fix: how I got rid of massive latency by changing the DNS settings - incognegro - 11-29-2007

Try OpenDNS & see if that helps.

http://opendns.com/


Re: Fix: how I got rid of massive latency by changing the DNS settings - Cary - 11-29-2007

All I can say is WOW!!! and thanks. I never considered DNS server as a fix for latency issues - I use Cablevision on Long Island, and it's always been OK, but not great. Just switched to OpenDNS, and pages load instantly!

Thanks!!!,

Cary


Re: Fix: how I got rid of massive latency by changing the DNS settings - Fritz - 11-29-2007

for some reason my Belkin won't do it.
it shows the changes under DNS after I applied them, but the log-in page still shows the automatic ones from Optonline.


Re: Fix: how I got rid of massive latency by changing the DNS settings - Jimmypoo - 11-29-2007

The Belkin I'm using is really bad - which is a surprise. I know it is on at least its 7th ROM revision......... This is the first Belkin product ever I've been disappointed with.


Re: Fix: how I got rid of massive latency by changing the DNS settings - lafinfil - 11-29-2007

Thanks for the info

I have been having latency issues with Verizon for the last few weeks and was going to start a thread

I've tried the open DNS so hopefully that will fix it.