What happens if you ensure resolv.conf is created in ip-up and
	removed in ip-down (and not there when ppp starts)?


                David/abs               abs@anim.dreamworks.com

    		       - Oakwood apartments -
     - $1300 a month and people steal your laundry - What a place -

On Mon, 5 May 1997 jhsterne@mindspring.com wrote:

> 
> Alright, I shouldn't be doing this.
> 
> Still, it raises a question.
> 
> Just for fun, I set up my NetBSD box (P450 yadda yadda yadda GENERICSBC-26 ...)
> to be its own nameserver.
> 
> Slave only, with forwarding to my normal nameservers.
> 
> (I wanted to see if caching would improve my speed by a few ms, but mostly
> I'm just playing).
> 
> It works fine.
> 
> The Unix System Administration Handbook advises not to set one's nameserver
> as the loopback address (127.0.0.1 for newbies).
> 
> I did, since my ISP only has dynamic IP addressing.
> 
> (That's the dumb part...)
> 
> In any event, it works fine, but ...
> 
> pppd takes a minute or so to start
> 
> (vs. like no time at all before)
> 
> Just wondering...
> 
> J.
> 
> (When I say start, I mean _start_, as in, it doesn't let go of the
> CPU for like a minute.  Obviously I can start it in the background,
> and not worry, but, again, I'm just curious.  Does this have something
> to do with the "Documented BSD Bug" mentioned in the Handbook?)
>