Slow server due to reverse lookup

Hi I have a tftp/ftp server running 2.2 in a lab environment. This thing is basically for people to ftp files to then tftp them down to routers etc for testing the code. Unfortunately both FTP and TFTP are extremely slow to connect (like over 20 seconds) and often the clients timeout. Once

Re: Slow server due to reverse lookup

On Mon, Jun 11, 2001 at 11:38:37AM +0100, Patrick Colbeck wrote: I am assuming that the server is doing a reverse lookup on all incoming tcp conections. Since the test lab has no DNS and the machines can have an ip address in a range that covers several thousand addresses (its a claa B

Re: Slow server due to reverse lookup

On Monday 11 June 2001 05:38, Patrick Colbeck wrote: I am assuming that the server is doing a reverse lookup on all incoming tcp conections. Since the test lab has no DNS and the machines can have an ip address in a range that covers several thousand addresses (its a claa B network) I really

Re: Slow server due to reverse lookup

I don't want to setup DNS as the possible range of IP addresses is huge. I would have to add entries for all the RFC 1918 address space, that would be hundreds of thousands of records to add to a DNS server. This is a lab where network engineers replicate routing issues or test new

Re: Slow server due to reverse lookup

Thanks Bud DNS in nsswitch was causing most of the problems but proftpd was still really slow even after that. For reference in case anyone else runs into this proftpd does reverse DNS and Ident against incoming addresses but you can switch it off in proftpd.conf thus: UseReverseDNS