NSD 3: slave too agressive
paul at xelerance.com
Sat Dec 16 22:09:13 UTC 2006
On Sat, 16 Dec 2006, Stephane Bortzmeyer wrote:
> I test NSD on a machine which is secondary for ~ 500 zones, many of
> them lame (for instance, the master no longer replies).
> When it occurs, nsd keeps asking and asking again and logs every
>  nsd: error: xfrd: zone 202.16.192.in-addr.arpa received error code REFUSED from 126.96.36.199
> Three requests, every ten seconds, and it does not stop even after
> several hours! Is it normal?
Unfortunately yes. NSD handles missing secondaries/primaries pretty badly. I was
hoping nsd3, which i haven't tested yet, would handle this better.
More information about the nsd-users