Quote:
Originally Posted by
brij123
Try to define almost all IPs, to which your server is connecting in /etc/hosts file.
Sorry to say this, but this is a VERY BAD advice.
First off, there is a reason for using DNS instead of local host lists and it is maintainability. Everything you write into
/etc/hosts you will have to change when the network changes. Chances are if this happens you forget to change one of the hundreds of hosts in one of the hundreds of
/etc/hosts files and you are in for all sorts of trouble.
Second, doing this is curing the symptom - the slow response - but not the root of the problem - the slow name server. It would be equally justified to say: switch off the system and your response time will drop to zero.
If i have anything learned at all in the 30 years of practicing the obscure art of handling computers it is this: if you solve a problem then do it in the most thorough way possible and accept no compromise! It is likely that a problem "solved" in any other way will come back haunting you when you least expect it and/or when it is the most unpleasant time to that happening.
@Thread-O/P: start monitoring the system (after, like stated above, making sure no hardware malfunction is the culprit) to find out in which way the system is slow: usual problems (and hence good starting points for investigation) are: memory, processor, network I/O, disk I/O.
Do a
vmstat to find out about memory/processor issues and
netstat to find out about network I/O. Use
iostat to get disk I/O statistics. If you don't know how to interpret the output of these tools report them back here, someone will be willing to do that for you.
I hope this helps.
bakunin