CUT ---
>
> Regards,
> Haim.
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On Behalf Of Miki Shapiro
> > Sent: Thursday, June 14, 2001 4:41 PM
> > To: Shachar Shemesh
> > Cc: Happy Linux Campers
> &
On Thu, 14 Jun 2001, Ariel Biener wrote:
> I wonder where you heard that from. As a thumb rule, expire is placed on
> TYPES on objects. You can define various types, be it images, html files,
> and others (like .gz/.zip/.rar/.bz2 and such)
.. We were talking about DNS entries, not MIME-defined H
ro
> Sent: Thursday, June 14, 2001 4:41 PM
> To: Shachar Shemesh
> Cc: Happy Linux Campers
> Subject: Re: DNS issue
>
>
>
> On Thu, 14 Jun 2001, Shachar Shemesh wrote:
>
> > An ISP places a cache to save on traffic. putting too low
> an expire time
> >
On Thu, 14 Jun 2001, Shachar Shemesh wrote:
> A value that should work OK, at least with some cases I've heard of, is
> 180 (three minutes). It should still give your client a reasonably
> updating service.
I wonder where you heard that from. As a thumb rule, expire is placed on
TYPES on objects
On Thu, 14 Jun 2001, Shachar Shemesh wrote:
> An ISP places a cache to save on traffic. putting too low an expire time
> spoils that.
>
> A value that should work OK, at least with some cases I've heard of, is
> 180 (three minutes). It should still give your client a reasonably
> updating servic
>
>foreign DNS's keep his entry cached more than the said
>"expire" (or is it "refresh"?) given 60 seconds, and when he updates my
>DNS, they don't update off me.
>
I have seen several cases of such behaviour, and not only with DNS.
It seems that the various caches throughout the internet do
