From owner-freebsd-questions Fri Aug 4 17:09:56 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA15374 for questions-outgoing; Fri, 4 Aug 1995 17:09:56 -0700 Received: from everest (dtr.rain.com [204.119.8.19]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA15360 for ; Fri, 4 Aug 1995 17:09:54 -0700 From: bmk@dtr.com Received: (from bmk@localhost) by everest (8.6.11/8.6.9) id RAA09355; Fri, 4 Aug 1995 17:07:45 -0700 Message-Id: <199508050007.RAA09355@everest> Subject: Re: iijppp auto & pine (fwd) To: rjbproc@Vir.com (Robert Burns) Date: Fri, 4 Aug 1995 17:07:44 -0700 (PDT) Cc: questions@freebsd.org In-Reply-To: from "Robert Burns" at Aug 4, 95 07:43:37 pm Reply-To: bmk@dtr.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 881 Sender: questions-owner@freebsd.org Precedence: bulk > On Fri, 4 Aug 1995, Mike O'Brien wrote: > > I have found that any reference to "localhost" causes a DNS lookup, > > if "resolv.conf" is in place. Maybe this is what you're seeing. > > > > > Mike, > Thanks for your response. > When I remove resolv.conf the problem goes away but causes DNS lookup > failures if I try to ftp to a remote site for instance. Any Ideas on how > to get around this? My resolv.conf file is set up as follows: > domain vir.com <---- my ISP > nameserver 199.84.154.65 <---- another DNS address > nameserver 199.202.197.65 <---- his address Check to see if your /etc/host.conf lists 'bind' before 'hosts'. If it does, switch them. Make sure localhost is listed in your /etc/hosts file. Of course, you'll want to put resolv.conf back the way it was. :) Another workable solution might be to run a caching nameserver on your machine.