There may be a race condition here:
```
(connection 1)
    time 1. A build starts with one build request in the queue.
    time 2. The build is almost done and is about the write its config file (it has not deleted the task yet)
        - At this point the `oregonstate.edu` zone will have been written to disk with up-to-date contents
(connection 2)
    time 3. A new record is created
        - It sees that there is already a task for a rebuild of its zone, it does not save a new Task object
(connection 1)
    time 4. The build completes and removes the Tasks it saw at the beginning of the build [0]

[0]:https://github.com/OSU-Net/cyder/blob/master/cyder/cydns/cybind/builder.py#L503
```

At `time 3` the record needs to make a new task (which will not be deleted since it didn't exist before the zone started) to ensure it causes a rebuild during the next build cycle.