Actually, that is exactly what we did for our server. It currently handles
over 3.8 million connections a week, and the load still hasn't stopped
climbing. We knew last May when we put this "round-robin" DNS into
effect that one system would not be able to handle the request load
to www.ncsa.uiuc.edu.
There are a couple of papers and presentations that either I or someone in
my group has done about what we have done. The code for DNS is also
available if you want that.
There are a couple of DNS round-robin products available, but we found
the ones that we tried round robin"ed" all the addresses for all systems.
We have 2 addresses for our cm5-a machine... cm5a and cm5-fddi. This
DNS code would round robin between those also... we also have 2 mx records
if one mail server is not found... deliver to the other... This was also
rotating between those. So, We just changed the DNS code so that it
would rotate ONLY on the addresses that we requested it to rotate on.
Pretty simple change.
Here is the URL for the paper written and presented at CERN:
and a presentation that I did at the Chicago WWW conference.
http://www.ncsa.uiuc.edu/InformationServers/Conferences/CERNwww94/www94.ncsa.html
http://www.ncsa.uiuc.edu/InformationServers/Conferences/CHIwww94/Start.html
If you need any more information on this, please let me know. Also let
me know if you want the DNS code that we did...
Michelle Butler
--------- Received message begins Here ---------
!! From [EMAIL PROTECTED] Tue Dec 27 12:10:06 1994
!! Received: from transarc.com by newton.ncsa.uiuc.edu with SMTP id AA04000
!! (5.65a/IDA-1.4.2 for mbutler); Tue, 27 Dec 94 12:10:04 -0600
!! Received: by transarc.com (5.54/3.15) id <AA01209>; Tue, 27 Dec 94 13:07:13 EST
!! Received: via switchmail; Tue, 27 Dec 1994 13:07:12 -0500 (EST)
!! Received: from transarc.com via qmail
!! ID </afs/transarc.com/service/mailqs/sq1/QF.4j05Qb30Bi81Q0vk4F>;
!! Tue, 27 Dec 1994 13:04:23 -0500 (EST)
!! Received: from po2.transarc.com via qmail
!! ID </afs/transarc.com/service/mailqs/sq1/QF.wj057Mb0Bi82A0vU9r>;
!! Tue, 27 Dec 1994 12:41:44 -0500 (EST)
!! Received: from po2.transarc.com via qmail
!! ID </afs/transarc.com/service/mailqs/q2/QF.Aj04mhL0Bi82457E5U>;
!! Tue, 27 Dec 1994 12:19:41 -0500 (EST)
!! Received: from inesc.inesc.pt (inesc.inesc.pt, [146.193.0.1]) by po2.transarc.com
(5.54/3.15) id <AA01302> for info-afs; Tue, 27 Dec 94 12:19:29 EST
!! Received: from nexus.inesc.pt by inesc.inesc.pt with SMTP;
!! id AA02110 (/); Tue, 27 Dec 1994 18:18:16 +0100
!! Received: by nexus.inesc.pt (NX5.67c/NeXT/STEP3.0)
!! id AA03832; Tue, 27 Dec 94 18:19:20 +0100
!! Date: Tue, 27 Dec 94 18:19:20 +0100
!! Message-Id: <[EMAIL PROTECTED]>
!! From: [EMAIL PROTECTED] (Hugo Andrade Cartaxeiro)
!! To: [EMAIL PROTECTED]
!! Subject: multiple WWW servers with single (DNS) name to access.
!! Status: R
!!
!!
!! Hi AFS'ers,
!!
!! My WWW tree is setup over AFS (big news, maybe yours too :-). This
!! way, I can have multiple (httpd) servers pointing to the same WWW
!! point.
!!
!! From here I would like to have a DNS name/alias (e.g. www.inesc.pt)
!! resolved into all the (real) WWW servers. On a one-query, one-server
!! basis. The criteria for resolving into a server instead of another,
!! would be something reasonable (availability? fastest? one at a
!! time?).
!!
!! Is this possible? Does anyone knows a named that act like that ? Or
!! any other solution for this problem?
!!
!!
!! tks in adv & a happy new year to you all,
!!
!!
!! --
!!
!! Hugo Andrade Cartaxeiro : INESC, Lisboa, Portugal. email: [EMAIL PROTECTED]
!! Tel: +351-1 310 02 49 Fax: +351-1 52 58 43
!!
!! This .sig was made w/ 94% recycled pixels. Please help our environment!
!!
Michelle Butler
National Center for Supercomputing Applications
AFS & Mass Storage
email: [EMAIL PROTECTED]
