Re: Dynamically Reducing TTL of few selected ResourceRecords

2012-09-30 Thread novosirj
OK well it helps with AD nameservers set to forward to some other nameservers 
for a domain, but I can't say why. 

Sent from my Verizon Wireless BlackBerry

-Original Message-
From: Barry Margolin 
Sender: bind-users-bounces+novosirj=umdnj@lists.isc.org
Date: Sun, 30 Sep 2012 21: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 use the cached data. I don't actually know for sure that that works 
> on a removed entry though. 

That's not correct. If you ask a caching server for ANY records, it will 
just return the types that happen to be in its cache.

-- 
Barry Margolin
Arlington, MA
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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


Re: Dynamically Reducing TTL of few selected ResourceRecords

2012-09-30 Thread Barry Margolin
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 though. 

That's not correct. If you ask a caching server for ANY records, it will 
just return the types that happen to be in its cache.

-- 
Barry Margolin
Arlington, MA
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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


Re: Dynamically Reducing TTL of few selected ResourceRecords

2012-09-30 Thread novosirj
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 
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 
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@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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


Re: Dynamically Reducing TTL of few selected ResourceRecords

2012-09-30 Thread Barry Margolin
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 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..

Each record can have an explicit TTL, e.g.

www 300 IN A 1.2.3.4

sets the TTL of the www record to 300 seconds. $TTL is just the default 
for records with no explicit TTL (which in most zone files is all of 
them).

-- 
Barry Margolin
Arlington, MA
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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


Dynamically Reducing TTL of few selected ResourceRecords

2012-09-30 Thread blrmaani
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@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users