>>>>> "ML" == Mike Lynchfield <[EMAIL PROTECTED]> writes:
ML> Well caching is the way to go., bu then again most of the current ML> solutions have this problem. ML> John smit has a DID.. 514 555 1234 and closes account.. did sleeps ML> for 3 months and new client Jane doe takes it.. ML> Now how long should caching be ? this is a big problem ATM because ML> some cache for 1 year others 1 day , they don't want to tell how ML> long nor provider an API update method. The actual records should have TTL's of a few hours, perhaps a day. The rest of the hierarchy can probably get away with longer TTL's, especially close to the root. It's the same thing with the root in regular DNS: You can cache the set of records in the root zone for a long long time, since noone is going to suddenly move all the .com nameservers. /Benny _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
