From owner-freebsd-questions  Fri Aug  4 17:07:00 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id RAA15170
          for questions-outgoing; Fri, 4 Aug 1995 17:07:00 -0700
Received: from aero.org (aero.org [130.221.16.2])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA15162
          for <questions@freebsd.org>; Fri, 4 Aug 1995 17:06:59 -0700
Received: from antares.aero.org ([130.221.192.46]) by aero.org with SMTP id <111119-1>; Fri, 4 Aug 1995 17:06:19 -0700
Received: from anpiel.aero.org by antares.aero.org (4.1/AMS-1.0)
	id AA25279 for rjbproc@vir.com; Fri, 4 Aug 95 17:05:53 PDT
To: Robert Burns <rjbproc@Vir.com>
Cc: questions@freebsd.org
Subject: Re: iijppp auto & pine (fwd) 
In-Reply-To: Your message of "Fri, 04 Aug 1995 12:43:37 PDT."
             <Pine.BSF.3.91.950804194240.321A-100000@zeta> 
Date: 	Fri, 4 Aug 1995 17:05:51 -0700
From: "Mike O'Brien" <obrien@antares.aero.org>
Message-Id: <95Aug4.170619pdt.111119-1@aero.org>
Sender: questions-owner@freebsd.org
Precedence: bulk

> 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?

I don't know of one.  Once you go with the DNS, the net had better be up;
/etc/hosts will only be used as a fallback after the DNS lookup times out
(i.e. if you just wait long enough things will proceed forward).  This
gives me fits because iijppp does the same thing; after the interface is
marked "UP", killing and restarting iijppp becomes a total pain, because
it does the selfsame thing.  You either have to temporarily move resolv.conf
out of the way and back again, or you have to wait out the DNS lookup
timeout.

Yuck.

Mike O'Brien