On 18.6.2014 19:19, Petr Spacek wrote:
On 13.6.2014 18:43, Petr Spacek wrote:
On 12.6.2014 17:49, Petr Spacek wrote:
On 12.6.2014 17:19, Simo Sorce wrote:
On Thu, 2014-06-12 at 17:08 +0200, Petr Spacek wrote:
Hello list,
I have realized that we need to store certain DNSSEC metadata for
On 13.6.2014 18:43, Petr Spacek wrote:
On 12.6.2014 17:49, Petr Spacek wrote:
On 12.6.2014 17:19, Simo Sorce wrote:
On Thu, 2014-06-12 at 17:08 +0200, Petr Spacek wrote:
Hello list,
I have realized that we need to store certain DNSSEC metadata for every
(zone,key,replica) triplet. It is
On 12.6.2014 17:49, Petr Spacek wrote:
On 12.6.2014 17:19, Simo Sorce wrote:
On Thu, 2014-06-12 at 17:08 +0200, Petr Spacek wrote:
Hello list,
I have realized that we need to store certain DNSSEC metadata for every
(zone,key,replica) triplet. It is necessary to handle splits in replication
On Thu, 2014-06-12 at 17:08 +0200, Petr Spacek wrote:
Hello list,
I have realized that we need to store certain DNSSEC metadata for every
(zone,key,replica) triplet. It is necessary to handle splits in replication
topology.
DNSSEC key can be in one of following states:
- key created
-
On 12.6.2014 17:19, Simo Sorce wrote:
On Thu, 2014-06-12 at 17:08 +0200, Petr Spacek wrote:
Hello list,
I have realized that we need to store certain DNSSEC metadata for every
(zone,key,replica) triplet. It is necessary to handle splits in replication
topology.
DNSSEC key can be in one of
