From owner-freebsd-hackers  Mon Apr 24 00:24:22 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id AAA24703
          for hackers-outgoing; Mon, 24 Apr 1995 00:24:22 -0700
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA24676
          for <hackers@freebsd.org>; Mon, 24 Apr 1995 00:24:00 -0700
Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP
	(5.67b+/DEC-Ultrix/4.3) id AA04246; Mon, 24 Apr 1995 09:23:43 +0200
Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP
	id JAA13231 for hackers@freebsd.org; Mon, 24 Apr 1995 09:23:42 +0200
Received: (from j@localhost) by jette.heep.sax.de (8.6.8/8.6.9) id JAA03600 for hackers@freebsd.org; Mon, 24 Apr 1995 09:19:32 +0200
From: J Wunsch <j@jette.heep.sax.de>
Message-Id: <199504240719.JAA03600@jette.heep.sax.de>
Subject: Re: Slip w/ 2.0
To: hackers@FreeBSD.org
Date: Mon, 24 Apr 1995 09:19:29 +0200 (MET DST)
Reply-To: hackers@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.950423205521.4581C-100000@haven.uniserve.com> from "Tom Samplonius" at Apr 23, 95 08:56:52 pm
Reply-To: joerg_wunsch@uriah.heep.sax.de
X-Phone: +49-351-2012 669
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 945       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> > cache     .                                                     root.cache
> > forwarders university.nameserver.ip_addr
> > slave                                
> 
>   Why don't you just add the line:
> 
> nameserver university.nameserver.ip_addr
> 
> 
> to your /etc/resolv.conf?  This way you don't have run and config named.

But this is different.  A caching nameserver has its own merits.  It
avoids the ask-back at the forwarder for each address you need.  This
really makes a difference if the SLIP line is e.g. saturated by a fat
ftp transfer, and the DNS packets would have to sit in the queue until
their time has come.  With a caching server, while almost no effort is
needed to configure it, it will quickly remember the cached addresses,
so the backoff will only happen on the first lookup of an address.

Alternatively, lowering the MTU will make the line responding ``more
quickly'', but at the cost of added overhead.

Jörg