[nsd-users] Questions about nsd-control zonestatus

[W.C.A. Wijngaards]

Hi Klaus,

On 17/01/18 16:38, Klaus Darilion wrote:
> one more question:

Yes this is correct behaviour, it is to make the force_transfer accept
any serial number (even with AXFR, and even the same serial number), by
wiping it away from the status.  The most recent serial is still being
served from the DNS port 53, but the status of that is removed to make
NSD accept the same serial again.

Normal transfer, 'nsd-control transfer', doesn't need to wipe that
status, and should show the values you were looking for in the
zonestatus output.  The transfer command is also faster: if the serial
number has not changed it'll conclude no transfer is needed, and it can
use IXFR to download only the differences.

Best regards, Wouter

> 
> # nsd-control zonestatus
> zone:   at
>         state: ok
>         served-serial: "2018011732 since 2018-01-17T15:23:57"
>         commit-serial: "2018011732 since 2018-01-17T15:23:57"
> 
> 
> 
> # nsd-control force_transfer at
> ok
> 
> # nsd-control zonestatus
> zone:   at
>         state: refreshing
>         served-serial: none
>         commit-serial: none
>         notified-serial: "0 since 2018-01-17T15:34:17"
>         transfer: "TCP connected to 83.136.34.20"
> 
> 
> IS this correct behavior? It is confusing that, during the transfer the
> served-serial and commit-serial is "none".
> 
> Thanks
> Klaus
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20180117/f6998671/attachment.bin>