View Full Version : FC2 slow on getting hostnames
pirofwil
19th June 2004, 08:18 AM
for some reason i am having trouble getting my host names to come up through redhat. I first thought it might be my router. So im not using one now and it still will not pick up the host names quickly. In windows it seems to be working perfectly. Im not sure what the problem is at all. Someone please help me out! TIA
ilja
19th June 2004, 08:27 AM
Mozilla says, that it might be the ipv6. so deactivate it with
echo "alias net-pf-10 off" >> /etc/modprobe.conf
If you want, I can find the source, where it stands
Picomp314
19th June 2004, 09:01 AM
can you give us the contents of your /etc/resolv.conf; yes there is no 'e' in resolve
pirofwil
19th June 2004, 03:31 PM
the contents of /etc/resolv.conf is as follows:
; generated by /sbin/dhclient-script
nameserver 24.151.8.210
nameserver 24.151.8.211
nameserver 66.189.130.5
nameserver 66.189.130.21
nameserver 66.189.0.29
nameserver 66.189.0.30
pirofwil
19th June 2004, 03:43 PM
even after putting in the echo, it still seems slow, although not as slow as before after a restart. I did at one point turn on the ipV6 but i turned it off. The mod file does have that that command listed, so that is not the problem. Im stuck!
SIKA
19th June 2004, 06:49 PM
Had the same problem as you, very slow "resolving hosts".
I finally fixed the problem today. I downloaded the 2.6.7 kernel source and recompiled a new kernel. Fixed alot of my problems in one hit. ie: nvidia driver problem, read Windows XP , slow internet.
Seems to be the only way to fix these problems in FC2.
SIKA
Badger
22nd June 2004, 02:32 AM
My guess is that one of your nameservers might be either busted or resolving slowly.
Best bet would be to run 'nslookup' without anything afterwards. Then enter:
server xxx.xxx.xxx.xxx where the xxx's are one of the entries from your /etc/resolv.conf. This will tell the program to not go thru the list, but rather to go directly to just the one server. Then enter a name of a site you would like resolved:
that.site.com
If the nameserver takes a long time in replying to your request, there is your problem child. Run thru your list and see which ones are taking some time to reply.
Also, I don't think its necessary to have all 6 of those listed. 2 or 3 are all you'll ever really need. Choose the fasted replying ones from the test above and delete the others.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.