Re: [nsd-users] About timestamps in logs and zonestatus
Hi Peter, All good. If the problem persists, let us know. - Jeroen On Wed, 2024-02-28 at 08:10 +0300, Peter Andreev via nsd-users wrote: > Hi Jeroen, > > I just realised that the version I use is very old -- 4.1. So first > what I should do -- updating it and only then come here , asking for > clarification. > > > вт, 27 февр. 2024 г. в 14:19, Jeroen Koekkoek : > > Hi Peter, > > > > NSD processes updates in batches. xfrd receives the [AI]XFR and > > schedules a reload for the main process, which in turn forks new > > serve > > children. The served-serial is updated after main reports success, > > the > > commit-serial (update written to disk) is updated before the reload > > (to > > explain the serials). > > > > The difference in timestamp can be explained by the fact that NSD > > looks > > up if the serial is still the latest after the TTL expires. If it > > is, > > the time is updated because the zone is renewed. > > > > What's the TTL of the zone? Where there any updates to the zone in > > the > > meantime? > > > > If the zone is expired in the meantime or the TTL is greater than > > the > > time printed, we can try increasing verbosity to spot an issue, or > > I'll > > have to dive into the code. > > > > - Jeroen > > > > > > On Tue, 2024-02-27 at 08:59 +0300, Peter Andreev via nsd-users > > wrote: > > > 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. > > > > > > ___ > > > nsd-users mailing list > > > nsd-users@lists.nlnetlabs.nl > > > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users > > > > > -- > Is there any problem Exterminatus cannot solve? I have not found one > yet. > > ___ > nsd-users mailing list > nsd-users@lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users ___ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
Re: [nsd-users] About timestamps in logs and zonestatus
Hi Jeroen, I just realised that the version I use is very old -- 4.1. So first what I should do -- updating it and only then come here , asking for clarification. вт, 27 февр. 2024 г. в 14:19, Jeroen Koekkoek : > Hi Peter, > > NSD processes updates in batches. xfrd receives the [AI]XFR and > schedules a reload for the main process, which in turn forks new serve > children. The served-serial is updated after main reports success, the > commit-serial (update written to disk) is updated before the reload (to > explain the serials). > > The difference in timestamp can be explained by the fact that NSD looks > up if the serial is still the latest after the TTL expires. If it is, > the time is updated because the zone is renewed. > > What's the TTL of the zone? Where there any updates to the zone in the > meantime? > > If the zone is expired in the meantime or the TTL is greater than the > time printed, we can try increasing verbosity to spot an issue, or I'll > have to dive into the code. > > - Jeroen > > > On Tue, 2024-02-27 at 08:59 +0300, Peter Andreev via nsd-users wrote: > > 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. > > > > ___ > > nsd-users mailing list > > nsd-users@lists.nlnetlabs.nl > > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users > > -- Is there any problem Exterminatus cannot solve? I have not found one yet. ___ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
Re: [nsd-users] About timestamps in logs and zonestatus
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 Im Auftrag von Peter Andreev via nsd-users Gesendet: Dienstag, 27. Februar 2024 06:59 An: nsd-users@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. ___ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
Re: [nsd-users] About timestamps in logs and zonestatus
Hi Peter, NSD processes updates in batches. xfrd receives the [AI]XFR and schedules a reload for the main process, which in turn forks new serve children. The served-serial is updated after main reports success, the commit-serial (update written to disk) is updated before the reload (to explain the serials). The difference in timestamp can be explained by the fact that NSD looks up if the serial is still the latest after the TTL expires. If it is, the time is updated because the zone is renewed. What's the TTL of the zone? Where there any updates to the zone in the meantime? If the zone is expired in the meantime or the TTL is greater than the time printed, we can try increasing verbosity to spot an issue, or I'll have to dive into the code. - Jeroen On Tue, 2024-02-27 at 08:59 +0300, Peter Andreev via nsd-users wrote: > 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. > > ___ > nsd-users mailing list > nsd-users@lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users ___ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
