This is a latency problem as far as I can tell. I'm having some serious problems making connections. It can take several seconds to make a connection in Firefox. I'm using Slackware 12.0. Just tested Konqueror- same problem. Once connections are made, loading speed is not a problem. Download speeds are accurate (~250 - 350 KB/s). Other computers on the network are not experiencing the same problems I am, so I'm fairly certain it's not modem or router related. No significant changes have been made over the past several days (with the exception of one- later). I experienced a loss of connection a few days ago, so I decided to reset everything and change my settings in an effort to bring it back up. That didn't work, so I just switched to the backup files, using the original configuration. Still no internet. Then, I made the change that fixed it. I previously only had one nameserver in /etc/resolv.conf. I added my ISP's second address, and my internet began working again, but now at a MUCH slower pace. Whereas pages previously loaded instantly, they are now taking upwards of 12 seconds just to loaded Google (and not even the personalized iGoogle!), which to me is rather ridiculous. Pinging Google.com returns some strange results, I think. It takes forever for it to begin reporting the times (around the same amount of time as trying to connect to their website), but it says it's only taking around 60ms. Additionally, zero packet loss is reported. My theory: my ISP's first nameserver is (or was) down, so my computer stopped resolving websites. I added the secondary nameserver, and it began working, but the second nameserver is not as efficient as the primary (at their office), so I suffer lower speeds. My computer is defaulting to the secondary address, whereas other computers (which were simply left down instead of adding a second DNS) are still on the primary nameserver, which is now working again. Is there a cache that the computer uses as far as what DNS you use is concerned? If so, where is it located so that I can clear it so that the computer defaults back to DNS1? If I'm completely off or if there's anything else that could be of use or possible, PLEASE let me know! As a note, I've searched the threads. But they all mysteriously died with no solution or the user not saying how he fixed it.

If you are set up to use dhcp, maybe just delete the 'network interface' and then reconfigure (using dhcp). The dns stuff will be taken care of by the server.

I don't use DHCP. It's too much epic fail.

I figured it out though. Apparently, DNS1 is still down (or just bogged down like crazy), and as it was the first in my list, Slack was trying to resolve hosts through it. So down or just too much traffic, it was taking forever to respond so Slack moved to the second DNS, at which point things properly resolved. Or the first one finally responded. Which is the case, I'm still not sure.

Simply switching the placement of the DNSs fixed the problem- putting the second one first now causes things to respond at a much faster rate.

Also...wtf...line breaks are NOT working at all. Except now they are. So again...wtf? =/

you really should have used a tool like wireshark or tcpdump. you'd have been able to see the dns requests failing instantly...

acid-

Thanks! Now I'll know for the future.