From owner-freebsd-questions Sun Apr 22 23:53:14 2001 Delivered-To: freebsd-questions@freebsd.org Received: from inbound0.mv.meer.net (inbound0.mv.meer.net [209.157.152.23]) by hub.freebsd.org (Postfix) with ESMTP id 4494137B43C for ; Sun, 22 Apr 2001 23:53:06 -0700 (PDT) (envelope-from david@usermode.org) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by inbound0.mv.meer.net (8.11.3/8.11.3) with ESMTP id f3N6r6p06405; Sun, 22 Apr 2001 23:53:06 -0700 (PDT) Received: from weathertop ([207.20.243.8]) by meer.meer.net (8.9.3/8.9.3/meer) with SMTP id XAA2636758; Sun, 22 Apr 2001 23:53:06 -0700 (PDT) Content-Type: text/plain; charset="iso-8859-1" From: David Johnson Organization: Usermode To: "Matthew Emmerton" , Subject: Re: Networking problem [solved] Date: Mon, 23 Apr 2001 00:00:40 +0000 X-Mailer: KMail [version 1.2] References: <01042215414303.00192@weathertop> <009001c0cb7c$eab02710$1200a8c0@gsicomp.on.ca> In-Reply-To: <009001c0cb7c$eab02710$1200a8c0@gsicomp.on.ca> MIME-Version: 1.0 Message-Id: <01042300004000.00179@weathertop> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it turned out that my ISP's nameserver wasn't working. I put an alternate nameserver address in resolv.conf and now everything is hunky dory. I thought that might have been it earlier, but I could ping the address, and when I booted into Slackware to verify, networking was okay. The catch was that I specified two nameservers in resolv.conf there, but neglected to add the alternate nameserver under FreeBSD. -- David Johnson ___________________ http://www.usermode.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message