Currently when an ownership record already exists for a record octoDNS manages, the ownership record will be overwritten regardless of the previous value.

I find the current behavior to be at least unintuitive. I understood the txt_value of an ownership record as the "owner" of the corresponding record. If octoDNS is not the owner of a record it wants to modify it should throw. If the current behavior is prefered, I think an "allow_takeover" parameter could make sense, which toggles the described behavior.

I'm aware that my use case of using multiple octoDNS instances is not supported but I can imagine this to be a problem in other scenarios as well (e.g. an external process setting ownership records).

If you consider this a bug, I'd be happy to contribute a fix. Just let me know.

Expected behavior

octoDNS will throw an error if it encounters an ownership records that does not belong to it.

Actual behavior

octoDNS will override the tag with its own ownership txt_value.