-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sebastian wrote:> Hi,
>
> I have some problem with the manuel update.
> The error message from "nsdc update" is:
>
> nsdc: Could not send notify for slave zone domain-xyz.xyz: not configured
> (with allow-notify: 127.0.0.1 or ::1)
>
> Than i have add allow-notify: 127.0.0.1 to the zone.
> The error message:
>
> [1162285294] nsd-notify[18352]: warning: timeout (5 s) expired, retry
notify
> to 127.0.0.1.
>
It looks like the NSD server is not running on the localhost.
What are you trying to do? Why do nsdc update? NSD will automatically
update secondary zones.
NSDC update is meant to be used to kick nsd into performing a secondary
update right now. For people with dialup connections or some such. Maybe
its a feature-bloated-feature and should not be in nsdc. Like nsdc notify.
If you want to update primary (master) zones you have to download/axfr
them manually.
Best regards,
Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFRxRkkDLqNwOhpPgRAt9BAJ9T3g/8+QoL9pONJm+DknXy8dIK7wCgiTxo
p5IyJw0afcJVCaEsKQ7c4xA=iA4B
-----END PGP SIGNATURE-----