This PR introduces the multi-part SPF/TXT handling. The underlying RR types are already defined so that the value is a list, but we currently ignore it and we attempt to parse/split the incoming value.
This is related to https://github.com/dnsimple/dnsimple-business/issues/1765, in particular to issues related to the TXT implementation. The current implementation is designed to prefer the parts over the single value, whenever the JSON contains a valid element with the expected value.
This PR introduces the multi-part SPF/TXT handling. The underlying RR types are already defined so that the value is a list, but we currently ignore it and we attempt to parse/split the incoming value.
This is related to https://github.com/dnsimple/dnsimple-business/issues/1765, in particular to issues related to the TXT implementation. The current implementation is designed to prefer the parts over the single value, whenever the JSON contains a valid element with the expected value.
Here's some examples.
1. TXT: Both
txtandtxtsexists,txtsis used