What problem does it solve? Custom-domain email setup often fails because a domain is registered at one provider (e.g., GoDaddy) while its nameservers are delegated elsewhere (e.g., Vercel, Cloudflare), causing registrar DNS APIs to return 'no zone' errors and leaving users with broken half-configured email. ## Core Features & Use Cases - Registrar vs DNS Host Diagnosis: Uses dig NS and whois to determine who is actually authoritative for a domain's DNS before attempting record writes. - Email Record Architecture: Guides safe addition of MX, SPF, DKIM, and DMARC records, which live in a separate namespace from A/CNAME records and cannot break a live website. - Architecture Matching: Helps choose between native platform mailboxes, forwarding to Gmail, or full Google Workspace based on available infrastructure, and states honest limitations when a setup is impossible. - Use Case: A user's GoDaddy API returns 'no zone' when adding MX records; this Skill identifies that nameservers point to Vercel, writes the records at Vercel instead, and verifies propagation with dig. ## Quick Start Diagnose why email records won't save on my custom domain and tell me where to configure MX, SPF, DKIM, and DMARC.