[Opendnssec-user] "not serving soa" warning message

Yuri Schaeffer yuri at nlnetlabs.nl
Fri Oct 28 08:15:30 UTC 2016

Hi Havard,

Thanks for the extensive report. I created an issue
https://issues.opendnssec.org/browse/OPENDNSSEC-853 which summarizes the
problem like this:

serial_xfr_acquired time in the xfrd state file is not updated properly.
This may cause an issue on restart if serial_xfr_acquired+expire < now.
The zone is then not served (despite having had a recent incoming XFR
and up to date SOA). After next XFR the zone will be served again.

We'll look in to it.


On 25-10-16 14:16, Havard Eidnes wrote:
> since I've had to restart OpenDNSSEC a few times lately due to
> the bug in the signer when a zone is removed, I've taken a look
> at the logs (I know, bad idea...), and I noticed a warning
> message from the axfr component in the signer saying "zone xxx
> expired at nnnnnnn, and it is now mmmmmmmm: not serving soa".

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20161028/aa1989e2/attachment.bin>

More information about the Opendnssec-user mailing list