Slow names resolution on CentOS 4.3

[EchoAlertcom]

Hello,

I have colocation space where I have several Windows, several RedHat FC4 and one CentOS 4.3 servers.

I am having an issue on the CentOS server with it resloving domain names. I have verified that the /etc/resolv.conf file has 'nameserver 123.123.123.123' which is the same name server that all the other servers use to resolve domain names.

The other servers resolve any domain name instantanously. This CentOS server takes 5-10 seconds but eventually resolves the name. I'm not sure if it's related but the throughput on this server when I do a bandwidth test is drastically slower than all the other machines. For example, on several other servers I can do a bandwidth test and it will show that I log about 20 Mbps (i'm in a Tier 1 datacenter) this CentOS box will log about 1 Mbps.

I have plugged the CentOS server into the same switch port as the other servers to eliminate that as an issue. These servers are all the same exact physical hardware.

I did some traceroutes with ip addresses and it seemed to show the same ms as the other servers.

Any suggestions of things to try to help solve this issue?

Warmest Regards,
Steve

 

[m4ilm4n]

Since your bandwidth test shows such a disparity, that would lead me to think the issue crosses all services and not just named; that would point me to look at something with the network adapter. As you say, pings and traceroutes are comparable, but larger packets are slower - maybe framesize or MTU settings are mismatched?

 

[EchoAlertcom]

the framesize and MTU should be default since I didn't change them.

Where do I check those values?

Are there standard values for those?

This server is just going to be doing web/ftp/mail.

Warmest Regards,
Steve

 

[ady2k]

Maybe you can try to install nameserver-caching.
That would help to resolve the names resolution.

 

[QatQat]

Have you got named running on the CentOS box?

Unless properly configured if needed, shut named down and try again.

What you are describing used to happen on old RH boxes (before RH8) and usually shutting named down or configuring it properly (as a caching DNS for example) would solve it.


Cheers

QatQat

Life is what happens when you are making other plans.