Re: Slow server due to reverse lookup

[Patrick Colbeck <pat.colbeck@bashq.org>]

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                   off
IdentLookups                    off

Now the thing connects instantaneously for all allowed methods :)

Mind you I wouldn't recommend doing this on a server connected to the
internet or one that had any data that you really cared about on
it. this one is just a staging and temporary storage area for
router/switch firmware so I dont really care if someone manages to
break it.

Thanks everyone for the suggestions.

Pat

>>>>> "Bud" == Bud Rogers <budr@sirinet.net> writes:

    Bud> 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 don't want
    >> to type all the ip addresses into the hosts file with dummy
    >> names. Is there anyway to turn of the reverse lookup and make
    >> life easier as this is a secure network not connected to the
    >> Internet ?

    Bud> You probably want to take dns out of /etc/host.conf and
    Bud> /etc/nsswitch.conf.  Both have good man pages that will
    Bud> explain what you need to do.  You might also want to set up
    Bud> NIS.


    Bud> -- Bud Rogers <budr@sirinet.net> http://www.sirinet.net/~budr
    Bud> All things in moderation.  And not too much moderation
    Bud> either.


    Bud> -- To UNSUBSCRIBE, email to
    Bud> debian-user-request@lists.debian.org with a subject of
    Bud> "unsubscribe". Trouble? Contact listmaster@lists.debian.org