Hi,
I'm running 1.4.3 and have one test record with 60 seconds TTL. The
RRSIG has a TTL of 60, too. Seems to work in this version, too.
Volker
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/l
Hi,
On 12/19/2013 02:04 PM, Ondřej Caletka wrote:
> Hi,
>
> Dne 19.12.2013 11:27, Matthijs Mekking napsal(a):
>> Something like that is not possible: All NSEC3 records TTL will be set
>> to SOA minimum value without exceptions. But if you only going to change
>> the record (not removing or adding
Hi,
Dne 19.12.2013 11:27, Matthijs Mekking napsal(a):
> Something like that is not possible: All NSEC3 records TTL will be set
> to SOA minimum value without exceptions. But if you only going to change
> the record (not removing or adding names), you don't need to worry about
> the NSEC3 records T
Hi,
On 12/19/2013 10:15 AM, Ondřej Caletka wrote:
> Hi,
>
> I'm using OpenDNSSEC 1.3.2. I'm trying to set a very low TTL (like 60)
> for one label in the zone (the IP address is going to change and I want
> to minimize downtime). I noticed, that in the signed file, all TTLs are
> clamped to the S
Hi,
I'm using OpenDNSSEC 1.3.2. I'm trying to set a very low TTL (like 60)
for one label in the zone (the IP address is going to change and I want
to minimize downtime). I noticed, that in the signed file, all TTLs are
clamped to the SOA minimum value set in KASP. When I lowered that value,
all RR
