How to override too-short TTL?

[Daemeon Reiydelle]

Duh, thanks. I can read the RFC (and have). Did you have something
constructive to say or do you specialize in repeating old emails?

The question was: is there a way to force a minimum time to live?  

I don't care if I violate some lamer's right to be an idiot. I care
about MY right to avoid complaints about "how slow the network is" when
my customer reads a page, then hits a "next" link, watches as 3 (or
more) separate DNS hits get resolved because the lamer has 3 different
url's for every darned page, each with a 2 minute timeout, and is too
stupid to install a free load balancer (e.g. OpenBSD) or to cheap to
install a commercial product (e.g. BigIP, Cisco or other).

Of course, if my customers would go away I wouldn't have any performance
problems, and could readily comply with the RFC. Darned customers.


Joseph S D Yao wrote:
> 
> On Mon, Aug 20, 2001 at 12:18:56PM -0700, Daemeon Reiydelle wrote:
> ...
> > Is there a way to force any cached ttl (obviously from a domain I am not
> > authoritative for) to have a "more reasonable" ttl like say 15 minutes?
> ...
> 
> Not and stay RFC-compatible [hence, not in BIND].  DNS is supposed to
> be a distributed database with data attributes determined by the owners
> of the data - no matter how lame they are.
> 
> [re: lame - the attributes, not the owners]
> 
> --
> Joe Yao                         jsdy at cospo.osis.gov - Joseph S. D. Yao
> OSIS Center Computer Support                                    EMT-B
> -----------------------------------------------------------------------
> This message is not an official statement of COSPO policies.

-- 
Daemeon Reiydelle Ph: 510.231.0880
Systems Engineer, Anthropomorphics Inc.