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
In article mailman.329.1349051635.11945.bind-us...@lists.isc.org,
blrmaani blrma...@gmail.com wrote:
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
BlackBerry
-Original Message-
From: blrmaani blrma...@gmail.com
Sender: bind-users-bounces+novosirj=umdnj@lists.isc.org
Date: Sun, 30 Sep 2012 17:33:45
To: comp-protocols-dns-b...@isc.org
Subject: Dynamically Reducing TTL of few selected ResourceRecords
Our development team complains about
In article mailman.331.1349053886.11945.bind-us...@lists.isc.org,
novos...@umdnj.edu wrote:
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
4 matches
Mail list logo
