From owner-freebsd-isp  Wed Oct  2 11:10:07 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA25462
          for isp-outgoing; Wed, 2 Oct 1996 11:10:07 -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 LAA25456
          for <freebsd-isp@freebsd.org>; Wed, 2 Oct 1996 11:10:04 -0700 (PDT)
Received: by pegasus.com (8.6.8/PEGASUS-2.2)
	id IAA02791; Wed, 2 Oct 1996 08:09:42 -1001
Date: Wed, 2 Oct 1996 08:09:42 -1001
From: richard@pegasus.com (Richard Foulk)
Message-Id: <199610021810.IAA02791@pegasus.com>
In-Reply-To: james@blacksun.reef.com (James Buszard-Welcher)
       "Re: RAID Controller Product" (Oct  2,  8:15am)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: freebsd-isp@freebsd.org
Subject: Re: RAID Controller Product
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

} Wouldn't there be a delay for clients still trying to reach
} your news server? If they have cached an IP address for
} news.wherever.com, and then you took it out of Round Robin,
} would there still be a finite number of clients trying to
} reach that IP address?  (Assuming they aren't looking to your
} nameserver and you didn't HUP it).
} 
} I'm pretty sure that Netscape doesn't (or at least didn't with
} 2.0) query the nameserver each time...
} 

A quick alias addition could fix that.  One box could check periodically
to see that another is still up,  when it stops responding you take over
for its IP address too.


Richard