DDNS updates and Failing Zone Transfers

[rick.morrison at fiberone.net]

We currently have a large domain that is being updated by DHCP that will not named-xfer.  When DDNS updates are turned off, the domain will transfer fine.

The problem appears to be that with the heavy volume and fast rate
of the dynamic updates, the serial number is getting incremented so quickly
on some zones that it occurs more frequently then the time necessary to transfer the zone.

  At the beginning of the zone transfer, serial number  1 goes to number two, so as soon as the SOA version changes, the primary closes the connection.
RFC 1035 section 6.3

Are there any solutions to solve this problem without turning DDNS off, or splitting the domain into subdomains?

Thanks,
Rick