< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] question about DNS time to live (TTL)


Yes - ttl defines how long the entry is cached.  DNS servers specify the
ttl, and it is returned with each query response.  The DNS interface has
a mechanism to configure a min ttl - that will override the ttl return
from the dns server.

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
> Dave Mason
> Sent: Wednesday, January 10, 2007 10:33 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] question about DNS time to live (TTL)
> 
> Hi,
> 
> I just have a quick question about how time to live is implemented in
> the
> DNS classes.  If the TTL has not yet expired, and a new lookup request
> comes
> in, does the DnsInterface remember the previous IP addresses that it
> found
> the last time it queried the DNS server, or does it always send a new
> request to the server?
> 
> Is that behavior configurable?  Any pointers about general TTL
behavior
> will
> help.
> 
> Regards,
> Dave
> 
> 
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel