Hi,
I'm using a zone with DNSSEC signing enabled that is updated using DDNS.
The update procedure is very simple and looks like this:
==> test_ddns.sh <==
#! /bin/sh
ZONE="example.org."
cat << EOF | nsupdate
server localhost
zone ${ZONE}
update delete ${ZONE} A
update add ${ZONE} 60 IN A
e.org. +timers`
> - Re-sign the zone `knotc zone-sign example.org`
> - Repeat your test
> ?
>
> Thanks,
> Daniel
>
> On 2018-10-17 23:25, Maximilian Engelhardt wrote:
> > Hi,
> >
> > I'm using a zone with DNSSEC signing enabled that is updated using
hree times in one
> second, with just the middle one actually changing the zone. If you
> think there is also a bug, please share more information to this,
> otherwise ok.
>
> Please let us know if the situation with not responding to DDNS appears
> again.
>
> Danke
socket due to occupied port, it would
> log something like
>
> 2018-10-18T13:14:12 error: cannot bind address 0.0.0.0@53 (address
> already in use)
>
> BR,
>
> Libor
>
> Dne 18.10.18 v 12:36 Maximilian Engelhardt napsal(a):
> > Hi Libor,
> >
> > I don
e DS records.
>
> It is also the safest way to obtain correct data for DS in parent
> because it gets generated by Knot DNS policy engine and minimizes risk
> of humar error.
>
> Petr Špaček @ CZ.NIC
>
> On 27. 10. 18 22:26, Maximilian Engelhardt wrote:
> > Hi L
ally (unless overriden by config) publishes CDS and CDNSKEY
> records in your zone. You can query your server and use them directly,
> the parent's DS shall be equal to your CDS.
>
> Libor
>
> Dne 26.10.18 v 18:24 Maximilian Engelhardt napsal(a):
> > Hi,
> >
> >
