From owner-freebsd-questions Fri Oct 2 13:03:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26398 for freebsd-questions-outgoing; Fri, 2 Oct 1998 13:03:06 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26370 for ; Fri, 2 Oct 1998 13:02:50 -0700 (PDT) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.1/8.8.8) with SMTP id PAA14481; Fri, 2 Oct 1998 15:08:00 -0500 (envelope-from jooji@webnology.com) Date: Fri, 2 Oct 1998 15:08:00 -0500 (CDT) From: "Jasper O'Malley" To: "Marc G. Fournier" cc: freebsd-questions@FreeBSD.ORG Subject: Re: WHO: invalid hostname? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Oct 1998, Marc G. Fournier wrote: > > What causes the below? > > lomar p6 invalid hostname 2:09PM 4 ssh -l marcus > > Misconfigured DNS such that a reverse DNS doesn't work? It happens when reverse DNS returns a hostname for which a forward DNS lookup fails. Happened to me last week at a customer site where their ISP had misspelt the hostname in a PTR record for one of the customers' IP addresses. > Is there anything > I can put onto my system to prevent connections from such? TCP Wrappers "unknown" or "paranoid" host specification should catch these, but it won't do you much good for something like sshd, which runs standlaone. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message