INWX: Add rules for TXT RRs containing double quotes and backslash

[eliheady]

INWX will not apply these RR changes and also does not error on the record content.

qoutes end up double-escaped. next preview: TXT ("in\\\"side" ttl=300) -> ("in\"side" ttl=300)

odd-numbered backslashes get stripped. next preview: TXT ("1backslash" ttl=300) -> ("1back\\slash" ttl=300) TXT ("3back\\\\slash" ttl=300) -> ("3back\\\\\\slash" ttl=300)

Release changelog section

Some examples:

• INWX: filter unsupported TXT RR content containing unbalanced quotes and backslashes

[eliheady]

@patschi what do you think about this? I am not sure blocking all of these records is the right thing, as it seems the characters are accepted if they are balanced in the records.

I can't work on it any further at the moment, but I was thinking a custom filter could be added to the INWX AuditRecords rules to check for the count of slashes and only block what INWX rejects. Then again, I think of what I've heard Tom say about avoiding too much error prevention and letting the provider APIs' errors inform users about problematic records (at least that's what I took from the comments that I can't find now lol)

[tlimoncelli]

I agree that we should let the API do its job. In the real world, nobody actually needs to create records that are so weird. We shouldn't put too much effort into solving a problem that doesn't happen.

[patschi]

I agree, let's keep the code base "simple" and not overcomplicate things. Should there ever be any valid use case or need having such TXT records, we can re-consider.