From owner-freebsd-isp  Wed Oct  2 14:05:58 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA07211
          for isp-outgoing; Wed, 2 Oct 1996 14:05:58 -0700 (PDT)
Received: from pegasus.com (pegasus.com [140.174.243.13])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07204
          for <freebsd-isp@freebsd.org>; Wed, 2 Oct 1996 14:05:54 -0700 (PDT)
Received: by pegasus.com (8.6.8/PEGASUS-2.2)
	id LAA03619; Wed, 2 Oct 1996 11:05:32 -1000
Date: Wed, 2 Oct 1996 11:05:32 -1000
From: richard@pegasus.com (Richard Foulk)
Message-Id: <199610022105.LAA03619@pegasus.com>
In-Reply-To: Joe Greco <jgreco@brasil.moneng.mei.com>
       "Re: redundant news systems" (Oct  2,  2:08pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: freebsd-isp@freebsd.org
Subject: Re: redundant news systems
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

} 
} > < 1 min DNS ttl = more anguish on the nameserver, non? I guess it would 
} > disturb the distribution of the round-robin... but for the length of
} > your ttl, is it going to choke up #2? 
} > How big is this client? ;)
} 
} I don't care too much about anguish on the nameserver, if it can't handle
} a dozen lookups per second (of the same record!) it needs to be rewritten
} anyways.
} 

Everyone should be concerned with reducing network traffic.

DNS is cached by everyone and everything, because although it seems
short and sweet, it's often slow.  Loading down nameservers unnecessarily
makes matters worse.

You and your systems aren't the only ones affected.


Richard