[nsd-users] nsdc notify should process in parallel

Matthijs Mekking matthijs at NLnetLabs.nl
Tue Apr 6 08:10:31 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Paul,

You are right that nsd-notify handles notifies sequentially and that
this delay can occur in specific situation.

However, note that NSD 3.x.x sends notifies automatically, implemented
non-sequentially. Also note that nsd-notify is deprecated since 3.x.x
and it is only still there because it is a useful aiding tool.

Best regards,

Matthijs

Paul Wouters wrote:
> 
> Hi,
> 
> If you have many zones, and you have a few zones with a broken/bad
> nameserver,
> then the notify process stalls using exponential backof, delaying all other
> zones sequentially as well. Example:
> 
> [root at vault nsd]# nsdc notify
> Sending notify to slave servers...
> [1269815681] nsd-notify[22093]: warning: timeout (1 s) expired, retry
> notify to 193.110.157.23.
> [1269815683] nsd-notify[22093]: warning: timeout (2 s) expired, retry
> notify to 193.110.157.23.
> [1269815687] nsd-notify[22093]: warning: timeout (4 s) expired, retry
> notify to 193.110.157.23.
> [1269815695] nsd-notify[22093]: warning: timeout (8 s) expired, retry
> notify to 193.110.157.23.
> [1269815711] nsd-notify[22093]: warning: timeout (16 s) expired, retry
> notify to 193.110.157.23.
> [1269815743] nsd-notify[22093]: warning: error: failed to send notify to
> 193.110.157.23.
> [1269815744] nsd-notify[22116]: warning: timeout (1 s) expired, retry
> notify to 193.110.157.23.
> [1269815746] nsd-notify[22116]: warning: timeout (2 s) expired, retry
> notify to 193.110.157.23.
> [1269815750] nsd-notify[22116]: warning: timeout (4 s) expired, retry
> notify to 193.110.157.23.
> [1269815758] nsd-notify[22116]: warning: timeout (8 s) expired, retry
> notify to 193.110.157.23.
> [1269815774] nsd-notify[22116]: warning: timeout (16 s) expired, retry
> notify to 193.110.157.23.
> [1269815806] nsd-notify[22116]: warning: error: failed to send notify to
> 193.110.157.23.
> 
> [ many more times repeated ]
> 
> The real fix I guess is to process zones parallel instead of serial.
> 
> Paul
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJLuux1AAoJEA8yVCPsQCW5hKwH/3MvrbLdp59pnLb930NvgHJ+
4qufxKB/WncCXWslZbZaem06SX/qe0EAtFUQKHolViZCPI1hC4/LEpGSUZwskaOe
lp1Lszn4PZ7ZA80vw9y7MmlmphlIbJvhYc2pFIQYaTu+4fnKGyPGDYKUIgA0sj5e
C4DsJ38bQ1154v9cFZK9XVNT6hE9J8ScQ/vvY+EFGq4Va9+7YVIZjIVKrpXvzv72
eBR4HVIMaqEM0onyeZwwddVbH0tiYektpsRnaVlXCRlX6UILdXW2e6d/gVyEmQMs
97MyTIv0grxId6NX7yvxA5dNaoOX2Vh9IYqnd2kZ1puDAwiwS7ZUwgGvxsFE/EY=
=93j5
-----END PGP SIGNATURE-----



More information about the nsd-users mailing list