From owner-freebsd-net@FreeBSD.ORG Sun Jan 1 03:07:41 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3048516A41F for ; Sun, 1 Jan 2006 03:07:41 +0000 (GMT) (envelope-from reverselogic@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 059BA43D78 for ; Sun, 1 Jan 2006 03:07:34 +0000 (GMT) (envelope-from reverselogic@gmail.com) Received: by nproxy.gmail.com with SMTP id o60so299427nfa for ; Sat, 31 Dec 2005 19:07:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uR5iYbd2oXR4PrOPBKXV1cqKzz1U9jJaRW3vbFLo2mY0Bih3NiltBAu5oBV9+kAXarzhX8tYkEV8PQcECfUFlQN9dLKBVFnYvA6l1XBkcetygXs1sFrno3q3D3rRAmO9BYAK7GR1VYNhcRpXx/mam4JPa9legoLcDp9ORIvupPg= Received: by 10.48.163.10 with SMTP id l10mr460161nfe; Sat, 31 Dec 2005 19:07:31 -0800 (PST) Received: by 10.48.217.10 with HTTP; Sat, 31 Dec 2005 19:07:31 -0800 (PST) Message-ID: Date: Sun, 1 Jan 2006 03:07:31 +0000 From: Paul To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: RE: FreeBSD 6.0 Release X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 03:07:41 -0000 On 12/31/05, Bill Vermillion wrote: > I know you'll find this hard to believe, but on Sat, Dec 31, 2005 > at 02:52 , Paul actually admitted to saying: > > > I've just installed FreeBSD 6.0 Release yesterday, I've spend the last > > two days trying to resolve a networking problem, the problem is this: > > when I try and connect to a domain or an IP for that matter, it takes > > several minutes for it to connect + receive the content. It doesn't > > seem to effect all addresses though, I've had no problems connecting > > to ftp://ftp.freebsd.org to download software etc., nor have I had any > > problems connecting to domains inside my LAN. > > > As far as I can tell, it isn't a dns problem because I can ping > > without any problems. > > That is out-going DNS. > > You said 'connecting problems' but only mentioned 'ftp'. > > Many ftp sites require a proper reverse DNS. But since you don't > have that with ftp.freebsd.org, but you do with other ftp addresses > it most likely is a DNS problem? > > Over the years I've noticed that many ISPs which give dynamic > addresses do NOT have reverse DNS mapped. That is wrong but there > is nothing you can do about it. > > From your few details [unless you can't connect to other sites > with http] I really do think it is a DNS problem. > > Bill > > Bill > -- > Bill Vermillion - bv @ wjv . com > Hi, The details I gave were a little vague, sorry about that. The problem I'm experiencing is effecting all protocols (ftp, http, irc, ssh, etc.) ftp.freebsd.org is an example of a domain which isn't effected, another of these is irc.chatjunkies.org (They're currently the only two I've found, which appear to be unaffected by the problem). I don't think that the problem is related to my ISP, because I've had 5/6 other operating systems (mainly Linux variants) before FreeBSD, and never before have I had the same problem. Now, the problems gets even stranger... This morning I decided to install 'links', it connected to a website without any problems at all. Previously I'd been doing my testing in firefox. Of course firefox still doesn't work, neither do (ftp, ssh, etc.) I've tried recompiling each of the applications, but they still don't work. Thanks, and happy New Year. - Paul.