zone loading errors can be ignored when reloading inline-signing zones
@dmahoney reported an odd error when trying to reload an inline-signing zone with a missing include file. The unsigned zone failed to load (as expected) but then it was still synced over to the signed zone, resulting in a loss of records.
This turns out to be because the result code from the reloading of the unsigned zone file (
ISC_R_FILENOTFOUND) gets stomped on before we called
zone_postload(), which then acts as if the reloading was successful and synchronizes the partially-loaded raw zone database into the signed zone database.
Once this error condition occurs there's no way to recover except blow away the signed zone and the unsigned journal and start over again.