Date: Tue, 19 Jun 2001 21:59:23 +0100 From: Richard Smith <rdls@rdls.net> To: Dan Armstrong <dan@beanfield.com> Cc: freebsd-questions@freebsd.org Subject: Re: Urgent help with Reverse Lookups and FTPD Message-ID: <20010619215922.C1074@gaia.home.rdls.net> In-Reply-To: <3B2F74D7.C057B32F@beanfield.com>; from dan@beanfield.com on Tue, Jun 19, 2001 at 11:50:47AM -0400 References: <3B2F74D7.C057B32F@beanfield.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 19, 2001 at 11:50:47AM -0400, Dan Armstrong wrote: > We are a small ISP, and just turned up a new webserver running Free4.3 > > Most of our customers live on private (192.168) addresses and I am > getting slaughtered with phone calls that they cannot ftp into their > sites, and it is because their ftp programs don't necessarily wait for > Free's ftpd to timeout doing the reverse lookup, for an address that of > course does not have any reverse information for it. If I add their > IP to the /etc/hosts BOOM they get in instantly. These thousands of > addresses are all dynamically assigned, so the hosts file fix is not > possible on this scale. Is there a way I can get it to stop? HELP! Just a random thought, if you made your name server authoritative for the zone "168.192.IN-ADDR.ARPA", it would fail the reverse lookup immediately. Rich. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010619215922.C1074>