Date: Mon, 8 Sep 2003 23:13:06 +0200 From: Andreas Klemm <andreas@freebsd.org> To: Jeremy Messenger <mezz7@cox.net> Cc: freebsd-hackers@freebsd.org Subject: Re: PUzzling sshd behaviour Message-ID: <20030908211306.GA50616@titan.klemm.apsfilter.org> In-Reply-To: <opru68l1a78ckrg5@smtp.central.cox.net> References: <3F589E94.1080508@xwave.com> <20030905154646.GA59881@rot13.obsecurity.org> <20030906213428.GF29217@spc.org> <3F5A8FDB.3050507@newsguy.com> <20030907015510.GG29217@spc.org> <20030908202727.GA49862@titan.klemm.apsfilter.org> <opru68l1a78ckrg5@smtp.central.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 08, 2003 at 03:59:51PM -0500, Jeremy Messenger wrote: > My solution is to install and setup dnscache to do the local DNS cache. DNS cache sounds like it caches DNS records after a successfull DNS query, right ? The problem at my clients project was, that the DNS server a) wasn't reachable from time to time because they played around with a pix firewall in a cat6k b) these particular OOB IPs and the sun's IPs were not in DNS database So ... I assume a dns *cache* wouldn't have brought any better functionality. We still would have needed a functionality in sshd, to turn off reverse lookup entirely ... The suns have already been secured by firewalls so no real need for this reverse lookup feature. Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030908211306.GA50616>