mirror of
https://github.com/Such-Software/adaptive-multi-protocol-gateway.git
synced 2026-10-17 07:31:32 +02:00
b041a78d29
The write path sent value1 and value2. Dynadot uses record_value1 and record_value2 in both directions and answered with "if record_type is entered, record_value1 must be entered", which reads like a missing value rather than a misnamed one. I corrected the reader for exactly this last time and left the writer alone, having concluded the two spellings differed. They do not. The unit test agreed with the code rather than with Dynadot, so it passed while every write was refused. That is now twice, in opposite directions, with a green suite each time. So this adds a round trip: read a zone, write it straight back, and assert nothing changed. It feeds the writer exactly what the reader produced, so a spelling the two do not share shows up as a value that vanished, and it fails against the code as it was. Worth the care because set_hosts replaces the whole zone. A record the reader drops or the writer misnames is a record deleted from a live domain, and the first zone we are writing is a shop. Co-authored-by: jw <jw@jwmacbookm5.local>