Repository navigation
feat(email): publish the SES DNS records through external-dns - #6225
Conversation
Company Email relays through Amazon SES with the custom MAIL FROM domain bounce.devantler.tech. Publish its MX and SPF records DNS-only from one platform-applied DNSEndpoint in the aws namespace, extend the explicit DNS-record allow-list with exactly that endpoint list, name and namespace, and let external-dns manage MX and TXT records. The mailbox domain's own SPF and DMARC records stay with their current owner. The identity's three DKIM CNAMEs join this DNSEndpoint once their tokens are readable. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅
|
✅
|
The company mail domain's SES identity exists, and its three Easy DKIM tokens are now readable. Add the matching DNS-only CNAMEs to the SES DNSEndpoint and to the explicit DNS-record allow-list, so SES can verify the domain. The committed DNSEndpoint passes the policy as written. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review 🤖 Generated with Claude Code |
Action not completed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
@coderabbitai review 🤖 Generated with Claude Code |
Action not completed
|
|
@coderabbitai review 🤖 Generated with Claude Code |
Action performed
|

Why
Amazon SES verifies the company mail domain, and AWS grants production access, only once the identity's DNS records are live. The platform publishes this domain's records through external-dns, but today it may publish only one fixed record, and only A, AAAA and CNAME records.
What
This publishes the SES records for company mail as DNS-only records: the bounce domain's MX and SPF records, and the identity's three DKIM records. Each is a new name, so no existing record changes; the mail domain's own SPF and DMARC records stay as they are. The platform's record allow-list admits exactly these records and nothing else.
Part of #5481
👉 After merge/promotion: SES verifies the domain on its own, and the open production-access case can then be answered.
🤖 Generated with Claude Code