This does not big harm on not-frequently updated zones, NOTIFY is simply delayed.
This helps on frequently updated (DDNS or [AI]XFR) zones - NOTIFY is not sent more often than once a second.

Libor Peltan authored 8 years ago and Daniel Salzman committed 8 years ago

instead, if obtaining key by keytag is necessary, we walk through all the matching keys and choose the appropriate one

- We have to cancel the timer before scheduling for a fixed time.
- We cannot cancel the timer if the zone is expired based on time,
  because the expire handler may not have been called yet.

The requestor can interrupt normal execution flow in case of
encountering for instance a malformed packet. The cleanup has to be
executed even in that case.

Libor Peltan authored 8 years ago and Daniel Salzman committed 8 years ago

This is achieved by using more procedures from normal signing.

Zone content update is now executed within the requestor. This allows
failing over to AXFR in case IXFR finished but the zone changes
coudn't be applied from any reason.

This is a fix of #498 a slightly ugly way:
we don't change the original ascii-formatted dname,
rather modify the log routine to check-add the trailing dot.