[NTLUG:Discuss] Slow when Connected to Net
Cameron, Thomas
Thomas.Cameron at bankofamerica.com
Wed Jun 16 09:17:45 CDT 2004
> -----Original Message-----
> From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org]On
> Behalf Of terry
> Sent: Wednesday, June 16, 2004 8:59 AM
> To: NTLUG Discussion List
> Subject: Re: [NTLUG:Discuss] Slow when Connected to Net
> Gateway doesn't need to be there, [in /etc/resolv.conf].
> Need nameservers, [domain name servers]
> and fastest one should be listed first, second one is only for backup.
> If you have a caching name server on your LAN, that one
> should be listed
> first, the remote one, as backup, on the next line.
> i.e.
> nameserver ####.##.#.#
> nameserver ###.##.#.#
One thing that I do on my laptop is to statically set a DNS server that I know works and then tell the DHCP client to not overwrite my resolv.conf file. To do that set PEERDNS=no in /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever interface you connect to your network with.
You can test to see if it is a DNS problem by using the host command against all three of the servers listed in your resolv.conf file like this:
host www.google.com 10.1.2.3
host www.google.com 10.1.2.4
host www.google.com 10.1.2.5
where 10.1.2.3 and the other addresses are the addresses in your resolv.conf. If one of them times out then you might have a bad DNS server and you should remove it from your resolv.conf file.
Thomas
More information about the Discuss
mailing list