Re: Why is my DSL for friggin' slow on Linux 9.1?

From: hachiroku (levin_at_ae86.gts)
Date: 03/02/05 

Date: Wed, 02 Mar 2005 02:55:18 GMT

On Wed, 02 Mar 2005 13:38:55 +1100, Centurion wrote:

> hachiroku wrote:
>
>> On Mon, 28 Feb 2005 23:50:24 -0600, mjt wrote:
>>
>>> hachiroku <levin@ae86.gts> wrote:
>>>
>>>> On Sun, 27 Feb 2005 19:58:54 +0000, hachiroku wrote:
>>>>
>>>> > ?
>>>>
>>>> I tried a few things mentioned here, no avail.
>>>>
>>>> Here's another clue: when I start Linux, right off the bat it's slow and
>>>> gets slower. I mean SLOOOOOOOW!!! I reboot, switch to XP, runs like a
>>>> champ; reboot back to Linux and it runs as fast as it ever did before...
>>>
>>> ... either something up with the NIC or maybe your
>>> bios is PNP ?!?!??!
>>
>> Here's another hint: it hangs for a while with a message 'resolving
>> host...' at the bottom of the browser.
>
> Check your DNS settings in /etc/resolv.conf
>
> You should have something like:
>
> search domain1.com domain2.com domain3.com
> nameserver 1.2.3.4
> nameserver 1.2.3.5
>
> The "search" line means it will append (in the order listed) those domains
> in an attempt to find the machine you refer to. For example, if you have
> "search google.com" and then punch "http://groups" into your browser, the
> resolver will try to resolve the raw hostname first (ie tell me the IP for
> "groups"), then append the domain and attempt to resolve that (ie tell me
> the IP for "groups.google.com"). It will search each of these domains
> until a valid IP is found, or it will return an error. ("it" being the
> resolver).
>
> This is all fine and dandy but where does it get the IP's from? Answer, the
> "resolver" lines. These point to the primary and secondary (possibly
> tertiary) name servers for your LAN or ISP. If you are NOT running a local
> DNS server, point these to your ISP.
>
> Finally, the last two files you should check are:
> /etc/nsswitch.conf
> /etc/hosts
>
> The first (nsswitch.conf) should probably have two lines that read:
> hosts: files dns
> networks: files dns
>
> This means look for IP/Hostname pairs in /etc/hosts first before consulting
> the DNS servers (as I described earlier).
>
> /etc/hosts will then allow you to over ride DNS or put addresses in there
> that there is no DNS record for (like other machines on your LAN - assuming
> no local DNS server).
>
> BTW - when you say your DSL is slow, do you mean transfer speeds or response
> time (like click on a link, wait, wait, wait, wait, zap! Page displayed)??
>
> Cheers,
>
> James

Thanks, James. Yes, that all makes sense. I used too know this stuff at
one point in time...

it's like you say, click, wait,wait,wait,wait, and then sometimes zzzap,
and sometimes zz...wait..zz..wait..a..wait...p. Really weird, and I don't
get this under Windoze...

It worked fine when I first loaded Linux. It has been getting
progressively slower as time goes by. Perhaps I'll back up and load
again...sigh. I'm used to doing that with Windoze!!!

Relevant Pages

  • Re: 300 requests/second for a non-existent name? Normal behavior or DOS?
    ... >Since firewall guys have to understand many of the protocol behaviors ... >opening the email would ask their ISPs DNS server for www.dot.mx.com. ... your negative cache ttl specifies, modulo caching issues on the resolver. ...
    (comp.security.firewalls)
  • Re: Hate to give up
    ... If your software requires DNS server settings, use: ... nameserver 207.69.188.185 ... Now try to ping yahoo.com and google.com. ... And, in fact, next PPP connection resolv.conf will almost certainly get ...
    (Ubuntu)
  • Re: named
    ... I always use the local IP address of the nameserver, ... This is a bug that existed for many years (it's even mentioned in the "DNS & BIND" book), but I thought it had been fixed in most flavors of Unix years ago. ... From man 5 resolver ... from some other system configuration database. ...
    (comp.sys.mac.system)
  • Re: named
    ... The BSD resolver has never worked for me with a server line of 12.0.0.1. ... I always use the local IP address of the nameserver, ... This is a bug that existed for many years (it's even mentioned in the "DNS & BIND" book), but I thought it had been fixed in most flavors of Unix years ago. ... from some other system configuration database. ...
    (comp.sys.mac.system)
  • Re: [Full-disclosure] DNS Cache Dan Kamikaze (Actual Exploit Discussion)
    ... Meaning you're back to square one. ... what happens if the resolver recv's a response after it's been told ... You *want* the nameserver to answer. ... You want it to answer - incorrectly - so that users are fooled into thinking they've been taken to the real site when in fact they been taken to a "mirror" of the real site, specially prepared for whatever nefarious purpose you have in mind. ...
    (Full-Disclosure)