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
..
api.go	Rename provider handles to *Provider (#914)	2020-10-26 09:25:30 -04:00
auditrecords.go	Re-engineer TXT records for simplicity and better compliance (#1063)	2021-03-07 13:19:22 -05:00
cscglobalProvider.go	MAINTENANCE: Unknown rtypes should return errors, not a panic (#945)	2020-11-13 16:32:40 -05:00