DragonFly users List (threaded) for 2006-10
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: ftpd is slow
You might want to run BIND locally and set 127.0.0.1 to be your main DNS
server. You'll gain the benefit of having a local cache of addresses and
(if you want to) you can have your server be authoritative for
192.168.1.xx
If you don't want to go to all that trouble, you can just add the
relevant hosts to /etc/hosts and see if that helps.
But it's possible I'm wrong about the lookups being the cause of the
problem since I can't find anything about ftpd or inetd doing reverse
lookups (or at least any way to disable them).
On 2006-10-30, Eugene wrote:
Eli Green wrote:
Is your FTP daemon doing reverse DNS lookups on an unfindable address?
That can significantly slow the connection down.
So, does FTP daemon look for addresses like 192.168.1.1 in a DNS base by
default? And how can I turn this off?
By the way, my DNS replies very slowly, too, and I have a problem with
my provider's DNS, because the last one drops about 30% of my machine's
requests.
I have an ftpd on both my server machines, one is running FreeBSD 4.7
and the pther one is running DragonFlyBSD 1.6.0.
The problem is that ftp replies on requests with a great delay in
both cases. The delay is about one minute, and there is no matter,
if the request came from a local network or from the Internet.
The CPU load of those machines is <10 %, and network load is rather
small too.
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]