4 commits

Author	SHA1	Message	Date
norman-zon	58a5a4bcf0	Remove length checking from TxtNoMultipleStrings (#1308) ... All functions in should test for only one condition. There already is a function that tests for long TXT records: TxtNoLongStrings. Add calls to TxtNoLongStrings in all providers that use TxtNoMultipleStrings, to keep functionality, except for NS1 and ClouDNS, which allow for any TXT record length, but not for multiple strings per TXT.	2021-11-23 14:35:01 -05:00
Anton Yurchenko	875bb02c4e	CLOUDNS: ClouDNS NOT allow multiple TXT records with same name (#1098) ... Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>	2021-03-21 14:13:41 -04:00
陸	bcad7c738b	CLOUDNS: Note that TXT records do not permit double-quotes. Fix typo (#1094) ... - Add AuditRecords for TXT NoDoubleQuotes	2021-03-14 12:16:53 -04:00
Tom Limoncelli	8dea9edc34	Re-engineer TXT records for simplicity and better compliance (#1063) ... TXT records are now handled different. 1. The raw input from dnsconfig.js is passed all the way to the provider. The provider can determine if it can or can't handle such records (auditrecords.go) and processes them internally as such. 2. The CanUseTXTMulti capability is no longer needed. * DSPs now register a table of functions * Use audits for txt record variations * unit tests pass. integration fails. * fix deepcopy problem * rename to AuditRecordSupport * Reduce use of TXTMulti * Remove CanUseTXTMulti * fix Test Skip * fix DO * fix vultr * fix NDC * msdns fixes * Fix powerdns and cloudflare * HEDNS: Fix usage of target field to resolve TXT handling (#1067) * Fix HEXONET Co-authored-by: Robert Blenkinsopp <robert@blenkinsopp.net> Co-authored-by: Jakob Ackermann <das7pad@outlook.com>	2021-03-07 13:19:22 -05:00