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

From: Centurion (spam_this_at_nowhere.com)
Date: 03/02/05 

Date: Wed, 02 Mar 2005 13:38:55 +1100

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 

-- 
panic: can't find /

Relevant Pages

  • Re: DNS cache poisoning - Wake up everyone!
    ... of whichever DNS resolver your web broswer is configured to use. ... dns-oarc.net name servers saw the lookups originating from. ... will not be vulnerable to this particular type of attack. ...
    (uk.comp.sys.mac)
  • Re: 300 requests/second for a non-existent name? Normal behavior or DOS?
    ... A lot of DNS clients are set to try a set of different suffixes if a query ... DNS servers and resolvers (they resolver is present on every ... >>from your DNS server should be cached for at least several minutes ... >>by the requesting entity, ...
    (comp.security.firewalls)
  • 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: Issue with DNS failover in domain
    ... The forwarders on DC1 and DC2 are pointing to another DNS server, ... As far as how the machine's resolver service behaves when a DNS server is down, ... Information on how a DNS Forwarder time-out works with using multiple Forwarder: ...
    (microsoft.public.windows.server.dns)
  • [Full-disclosure] Linux: telnet/ssh and other clients can connect to wrong host in case of mixed
    ... During digging behind strange DNS requests receiving my DNS server I ... debug1: Applying options for * ... Probably other standard resolver using clients or servers (on ... [successful AAAA] ...
    (Full-Disclosure)