httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Murcko <ch...@telebase.com>
Subject Re: Microsoft's "amazing" web servers
Date Tue, 16 Jul 1996 03:41:03 GMT
Nathan Schrenk liltingly intones:
> 
> I have just viewed some behavior at www.msnbc.com that I have not seen 
> before, and I thought other members of this list might be interested, 
> although this is off-topic.
> 
> www.msnbc.com currently resolves to 9 different IP addresses.  Some of 
> those addresses are serving HTTP traffic on port 80, and some of them are 
> refusing connections.  The browser I'm using, Netscape 2.02 for Solaris, 
> doesn't behave very well when trying to connect to this site.  Evidently, 
> Netscape looks at the first address it gets from the DNS and attempts to 
> connect to it.  When that fails, it pops up an error message.  When I use 
> Solaris' telnet client to connect to port 80 on www.msnbc.com I will get 
> one or more "Connection refused" messages as telnet goes through the list 
> of addresses attempting connections and then I'll get a connection that's 
> accepted that I can use.
> 
> So who is at fault here?  Is Microsoft at fault for having servers that 
> are down, or is Netscape at fault for not checking each one of the 
> addresses that are in the DNS?  Or perhaps the failure of my browser to 
> communicate to this server is just a casualty of different, but not 
> technically incorrect, interpretations of various Internet standards?
> 
This looks like round robin DNS on too few servers to handle the load.
A load balancing DNS would take care of this, better at least.

chuck
Chuck Murcko	N2K Inc.	Wayne PA	chuck@telebase.com
And now, on a lighter note:
In Boston, it is illegal to hold frog-jumping contests in nightclubs.

Mime
View raw message