Slow resolving hosts in anything HELP???

[garymayor]

This has been driving me mad for ages i've tried adding the

alias net-pf-10 off

to /etc/modprobe.conf

and rebooted. This is the usual answer that people are getting and most of the time it works for them but for me it's still slow as hell.

I'm on Fedora Core 3 going through a gateway machine running Windows XP ICS. There are other Windows machines on the network and they resolv hosts at lightening speed. But is XP causing just Linux machines to go slow at resolving domains.

ANY IDEAS???

Thanks

[macemoneta]

Usually, slow DNS resolutions means that one of the DNS servers you are using (the first in the list) is not responding. As a result, it times out and then the second DNS server responds. Try removing the first DNS server you have configured. If you only have one, it may be overloaded; see if your service provider has another you can specify.

[malcidragon]

Use a caching DNS server on the gateway (install a decent OS on it ;) wouldn't hurt either)
this way it should speed up the DNS queries by a heck of a lot,
or install a caching DNS server on the fedora box and then use 127.0.0.1 as the first nameserver

Cheers

Malc

[garymayor]

Hi,
That would be great but i'm unable to change the os as the user of that computer won't do it. Also adding my own caching nameserver doesn't seem to work as my /etc/resolv.conf contains this and whenever i change it it just changes it back after reboot

search mshome.net
nameserver 192.168.0.1

how on earth do i stop /etc/resolv.conf from changing my configuration after reboot?

Thanks

[ewsforos]

dhcpcd does that for you. Whenever it gets the info of your network configuration from the dhcpd it appends /etc/resolv.conf.

There are several ways to do that from configuration options on dhcpcd to the easy&dirty way. (remove all write permissions from the file)

[garymayor]

Ah yes forgot about write permissions will give it a go!