aws-route53-dns

Automates AWS Route 53 DNS record management for SES email verification and domain delegation.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ndestates/ndestates-website --skill aws-route53-dns-ndestates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-route53-dns
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/aws-route53-dns
Command: npx skills add https://github.com/ndestates/ndestates-website --skill aws-route53-dns-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up DNS records for Amazon SES email (verification TXT, DKIM CNAMEs, SPF, DMARC, MX) is error-prone when done manually through registrar dashboards, leading to email deliverability failures and DNS drift. This Skill automates the entire Route 53 workflow with AWS CLI commands and JSON change batches. ## Core Features & Use Cases - Hosted Zone Management: Create or identify Route 53 hosted zones and delegate nameservers from registrars like DigitalOcean. - SES Email Records: Apply verification TXT, three DKIM CNAMEs, SPF, DMARC, and MX records via idempotent UPSERT change batches. - Verification & Drift Control: Confirm propagation with dig, poll SES identity status, and enforce least-privilege IAM scoped to the hosted zone. - Use Case: After running SES domain verification, apply the full email record set for ndestates-io.com in one command, then verify DKIM and DMARC status without touching a registrar UI. ## Quick Start Ask the AI to create a Route 53 hosted zone and apply the full SES email records (verification, DKIM, SPF, DMARC, MX) for your domain.

Frequently Asked Questions about aws-route53-dns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up SES email DNS records in Route 53?▼

Run aws ses verify-domain-identity and verify-domain-dkim to get tokens, then apply a JSON change batch with aws route53 change-resource-record-sets containing the verification TXT, three DKIM CNAMEs, SPF, DMARC, and MX records.

How do I delegate nameservers from DigitalOcean to Route 53?▼

Create a hosted zone with aws route53 create-hosted-zone, copy the four NS values from the DelegationSet output, and set them at your registrar. Propagation can take 24-48 hours; confirm with dig NS and dig +trace.

Can I add an SPF record if a TXT record already exists at the apex?▼

Route 53 best practice allows only one SPF TXT record per name. Merge the include:amazonses.com value into the existing SPF record instead of creating a second TXT at the root.

How do I verify DKIM and domain verification status in SES?▼

Use aws ses get-identity-verification-attributes and get-identity-dkim-attributes for your domain, and confirm propagation locally with dig TXT and dig CNAME queries against the record names.

What IAM permissions does Route 53 DNS management need?▼

A least-privilege policy allowing ListHostedZones, GetHostedZone, ListResourceRecordSets, and ChangeResourceRecordSets, scoped to the specific hosted zone ARN rather than a wildcard resource.