cache problem?

[m0nk]

Joel Callahan wrote:
> A business associate used to use a company for both his web hosting as well
> as his isp. He switched web hosting but kept the company for his isp.
>
> Now, whenever he (or ANYONE ELSE THAT USES THAT ISP) that tries to access
> his site via the domain name, they get the OLD SITE! (the old files are
> still there, I presume). As a work-around, I had him enter the IP address
> and it then brings it new site up properly.
[snip]
> Any thoughts?

sounds like they still have the entries in their DNS server and haven't
made the appropriate changes.

--
Hello. My name is Oedipus. You are my father. Prepare to die.

[Joel Callahan]

Here is the problem:

A business associate used to use a company for both his web hosting as well
as his isp. He switched web hosting but kept the company for his isp.

Now, whenever he (or ANYONE ELSE THAT USES THAT ISP) that tries to access
his site via the domain name, they get the OLD SITE! (the old files are
still there, I presume). As a work-around, I had him enter the IP address
and it then brings it new site up properly.

Everyone else that sees the site (that does NOT use this internet provider)
sees the new, correct web site.

The tech support guys have told me the following:

They are using FreeBSD
They are using Apache Web Server
They say they are using the latest version with all the patches, fixes, etc.

Here is what they observe:
Internet Explorer: with cache turned off, it resolves properly
Internet Explorer: cache turned on, it finds old site
Netscape: with cache off, it finds new site
Netscape: with cache on, it can't find anything

They are at a complete loss as to why this is happening. Their observations
point to a cache issue, but the cache should expire after 7 days, right?

Someone here thought if they reset/flushed their router's table (they are
using a Bay router), then it would force the router to request a fresh list
from upstream. He said they had a power outage last week, and all the
routers were reset.

Any thoughts?

-Lucy
lu...@dhimaging.com.au

[Bill Moran]

What does God need with a starship?

Ok - first off ... determine if it's a DNS problem or an HTTP problem.
When you ping the domain name (i.e. www.mysite.com) does the ping line
give you the proper IP address for the server? If it's still giving you
the old IP address, forget about Apache/www/FreeBSD and tell whoever is
in charge to get the DNS entries fixed.
If the DNS is OK, then it's an HTTP problem of some sort.
How many systems have you tested this on? Caching rules are very fickle.
Just because your web server says the file expires in 3 days doesn't
mean the browser will handle it properly. IE for one has an option to
NEVER check for updated files. In that case, the only thing you can hope
for is that your clients are smart enough to hit refresh every now and
then.
Find out from the old provider what their headers were saying. This will
give you a good idea of how long MOST caches will hold the old files.
When the files expire, the browser (or proxy) will go looking for new
pages and find the new site.
As long as it's not a DNS problem. Make ABSOLUTELY sure the DNS is
correct first or you'll never get the thing working.

-Bill

[Joel Callahan]

Thanks guys... I'm passing this info along.

Appreciate your time and answers...

-Lucy

Joel Callahan <jo...@dhimaging.com.au> wrote in message
news:1o_n5.34790$c5.9...@newsfeeds.bigpond.com...