Update Resend template with optional CAA record

[cassiozen]

Description

Updates resend.com.click-tracking.json (v1 → v2):

• Added new CAA record (0 issue "amazon.com" at @) in caa group
• CNAME host changed from @ to %clickTrackingSubdomain%
• Added groupId: "click-tracking" to CNAME

Some registrars (e.g. Vercel) auto-create restrictive CAA records on domains, which blocks Amazon CloudFront from issuing the SSL certificate needed for the click-tracking reverse proxy.

The CAA record is in its own caa group (separate from click-tracking) so we can only apply it when needed.

Updates resend.com.mail.json (v5 → v6):

• logoUrl updated.

Templates updated:

• resend.com.mail.json v5 → v6
• resend.com.click-tracking.json v1 → v2

Type of change

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

• Template functionality checked using Online Editor
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

• syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
• warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
• syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
• no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC) — N/A, no TXT records added
• no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary — CAA value is fully static (0 issue "amazon.com")
• no bare variable is used as the full host label — CAA record uses @, no variables
• no variable is used in the host field to create a subdomain — CAA record uses @, no variables
• %host% does not appear explicitly in any host attribute
• essential is set to OnApply on records the end user may need to modify or remove without breaking the template (e.g. DMARC) — N/A, no DMARC or user-modifiable records

Online Editor test results

Editor test link(s):

For resend.com.click-tracking.json

solo click tracking subdomain flow: Test resend.com/click-tracking example.com/@

solo click tracking subdomain flow (w/ Host): Test resend.com/click-tracking example.com/newsletter

solo click tracking subdomain + CAA flow Test resend.com/click-tracking example.com/@

For resend.com.mail.json (logo update)

Test resend.com/mail example.com/newsletter

Test resend.com/mail example.com/@

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

resend.com.click-tracking.json

Level	Code	Note
info	DCTL1016	unexpeceted record type

resend.com.mail.json

Level	Code	Note

[github-actions]

PR Description Check Passed

All required sections are filled in correctly.

Details

  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 5 link(s) found
  OK  Template coverage: all 2 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED