Dynamically Reducing TTL of few selected ResourceRecords

novosirj at umdnj.edu novosirj at umdnj.edu
Mon Oct 1 01:11:11 UTC 2012


A secret a co-worker taught me is to dig ANY on a record. Chances are most queries are A queries only. If you have HINFO records or anything else, it will not use the cached data. I don't actually know for sure that that works on a removed entry though. 

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: blrmaani <blrmaani at gmail.com>
Sender: bind-users-bounces+novosirj=umdnj.edu at lists.isc.org
Date: Sun, 30 Sep 2012 17:33:45 
To: <comp-protocols-dns-bind at isc.org>
Subject: Dynamically Reducing TTL of few selected ResourceRecords

Our development team complains about waiting for an hour for the deleted resource records to disappear from recursive resolver cache.

I thought of changing the $TTL value to 1 for that zone but realize that its not efficient. 

Are there any BIND specific options to support this? I know I can have a cron to flush cache of selected records, but a BIND option to support this would be nice..


Thanks
Blr
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


More information about the bind-users mailing list