On Tue, Jun 23, 2009 at 10:10 PM, Mark Andrews wrote:
> Yes the updates are slow because we had some disasters with the
> automation but we intend to turn that on again soon. That being
> said you really do need to check that the new data has been published
> before you start the wait periods. Th
In message , R Dicair
e writes:
> On Tue, Jun 23, 2009 at 8:10 PM, Mark Andrews wrote:
> >
> >Even if the update were published on the master instananeo=
> usly
> >you still need to wait for the zone to transfer to all the
> >slaves and for the old DLV records to timeout of
On Tue, Jun 23, 2009 at 8:10 PM, Mark Andrews wrote:
>
> Even if the update were published on the master instananeously
> you still need to wait for the zone to transfer to all the
> slaves and for the old DLV records to timeout of caches.
Even 24 hrs after? My zone ttls are s
In message , Chris Tho
mpson writes:
> On Jun 23 2009, R Dicaire wrote:
>
> >Hi folks...Yesterday I performed a DNSSEC KSK rollover, updated DLV
> >with the new keys, and confirmed successful updates to DLV via their
> >script. According to DLV all zones are good. Upon completing this, I
> >then
On Jun 23 2009, R Dicaire wrote:
Hi folks...Yesterday I performed a DNSSEC KSK rollover, updated DLV
with the new keys, and confirmed successful updates to DLV via their
script. According to DLV all zones are good. Upon completing this, I
then removed the old keys from the DLV db for each zone I
Hi folks...Yesterday I performed a DNSSEC KSK rollover, updated DLV
with the new keys, and confirmed successful updates to DLV via their
script. According to DLV all zones are good. Upon completing this, I
then removed the old keys from the DLV db for each zone I have
registered.
Now when I attempt
6 matches
Mail list logo
