Re: www clients and dns

• Mail folder: WWW Talk Oct 93-present
• Next message: Dave_Raggett: "Re: New tag (or old?)"
• Previous message: Ron D. Appel: "log analysis tools"
• In-reply-to: Marc Andreessen: "www clients and dns"

Message-id: <199310011625.AA18022@library.ucsf.edu>
From: dcmartin@library.ucsf.edu (David C. Martin)
Organization: UCSF Center for Knowledge Management
Email: dcmartin@ckm.ucsf.edu
Phone: 415/476-6111
Fax: 415/476-4653
To: marca@ncsa.uiuc.edu (Marc Andreessen)
Cc: www-talk@nxoc01.cern.ch
In-reply-to: Your message of Thu, 30 Sep 1993 18:34:11 -0500
	<9309302334.AA24315@wintermute.ncsa.uiuc.edu> 
Subject: Re: www clients and dns 
Date: Fri, 01 Oct 1993 09:21:51 PDT
Sender: dcmartin@library.ucsf.edu

I agree, but you may want to invalidate the members of the cache after a
certain period of time to avoid DNS mismatch.  This may also be
something that could be folded into the authorization layer.

dcm
--------
Marc Andreessen writes:

It seems to be the experience of quite a few Mosaic 2.0pre4 users (now
that the status line tells you exactly what's happening at each stage
of a connection and data transfer) that DNS hostname lookups often
take a very long time in relation to the actual time needed for the
connection and data transfer.

This brings up an interesting question: should we therefore maintain a
cache of hostnames and IP addresses on the client side to try to paper
this (non-Mosaic) problem over, or should we leave it up to DNS to be
fast or slow as it wishes at each installation and put the burden on
the DNS and network admins to make sure it gets faster if users are
unhappy?

Marc