From owner-freebsd-current Tue Feb 3 21:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19049 for current-outgoing; Tue, 3 Feb 1998 21:35:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19042 for ; Tue, 3 Feb 1998 21:35:01 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.7) with SMTP id WAA26686 for ; Tue, 3 Feb 1998 22:44:20 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <00b001bd3127$2470cde0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: current.freebsd.org unable to connect Date: Tue, 3 Feb 1998 22:41:21 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" From: spork Date: Tuesday, February 03, 1998 2:11 PM >You should make sure that your machine's reverse lookup is happening OK. >The snap server seems to tend toward the "super-paranoid". It nukes >mismatches and things that just aren't reversed... > > I just did a nslookup from "a.root-server.net", and it was able to return both the name and IP address of my computers. So I don't think that's the problem. Maybe, Vince is correct that it is a problem at MAE-West. Guess I'll have to try tomorrow. Thanks Scot