[nsd-users] About timestamps in logs and zonestatus
Klaus Darilion
klaus.darilion at nic.at
Tue Feb 27 19:44:29 UTC 2024
May it be that the NSD process was restarted, so zonestatus output is the time where NSD finished loading the zone?
Regards
Klaus
--
Klaus Darilion, Head of Operations
nic.at GmbH, Jakob-Haringer-Straße 8/V
5020 Salzburg, Austria
Von: nsd-users <nsd-users-bounces at lists.nlnetlabs.nl> Im Auftrag von Peter Andreev via nsd-users
Gesendet: Dienstag, 27. Februar 2024 06:59
An: nsd-users at lists.nlnetlabs.nl
Betreff: [nsd-users] About timestamps in logs and zonestatus
Dear All,
Please help me understand why timestamps in logs are different from those in nsd-control zonestatus output:
served-serial: "2024022603 since 2024-02-27T08:07:51"
commit-serial: "2024022603 since 2024-02-27T08:07:51"
Feb 26 18:47:34 slave-server nsd[780]: zone testzone.test. received update to serial 2024022603 at 2024-02-26T18:47:33 from 192.168.10.10 TSIG verified with key mytsig of 6517 bytes in 3.8e-05 seconds
Feb 26 18:47:34 slave-server nsd[777]: zone testzone.test serial 2024022601 is updated to 2024022603.
--
Is there any problem Exterminatus cannot solve? I have not found one yet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20240227/60f03450/attachment.htm>
More information about the nsd-users
mailing list