14:25
To:
Subject: Re: Dynamically Reducing TTL of few selected ResourceRecords
In article ,
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
In article ,
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 know for sure that that works
> on a removed entry t
eless BlackBerry
-Original Message-
From: blrmaani
Sender: bind-users-bounces+novosirj=umdnj@lists.isc.org
Date: Sun, 30 Sep 2012 17:33:45
To:
Subject: Dynamically Reducing TTL of few selected ResourceRecords
Our development team complains about waiting for an hour for the deleted
res
In article ,
blrmaani 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 but realize that its
> not efficient.
>
> Are there any BIND spe
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 ha
5 matches
Mail list logo
