RE: [cobalt-users] FW: Name-based host problem

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

At 01:05 PM 1/10/00  ISP wrote:

> Thanks Jeff...this is what I was looking for. I think I can figure it out
> from here.

You're welcome.

> How bad is AOL on honoring the TTL? This domain was updated last Thursday
> and AOL
> is not even displaying the correct page for the IP site.

I don't know.  But I know they have huge caches which they update at their 
own speed.  They do it to keep traffic down, I'm sure.  But they should 
still do an immediate lookup of your NEW domain record if they don't 
already have it.

Here's what should happen:

Your browser asks for <www.newdomain.com>.

There's no record for <www.newdomain.com> in their dns cache.

Their dns queries the root servers for the authoritative name-server for 
<www.newdomain.com> and get back the dns of the athoritative name-server, 
in this case <ns.yournameserver.com>.

Their dns queries <ns.yournameserver.com> and gets the dns record, which it 
stores in their cache until the expiration, which is based on the record's 
ttl field.

The reality, if I may misquote out of context from the movie "Titanic", is 
slightly different.

> Does AOL 5.0 support name-based?

As far as I know only very old browsers <= versions 2.0 don't support 
name-based hosting, but it's still a good idea to consider that some people 
may be using them, especially on early Apple and Win3.1 platforms.

> I thought it was using IE5?

The latest one may be using Mozilla, now that they've bought 
Netscape.  However, since I don't use them, I don't know.

Jeff

--
Jeff Lasman, nobaloney.net
<jblists@xxxxxxxxxxxxx>
<www.nobaloney.net>, <www.mailtraqna.com>, <www.email-lists.com>