primitive-domains

Put Primitive on the user's own domain: claim it, publish the DNS records Primitive generates, verify, and keep it healthy. Once verified, the domain receives mail into Primitive and can be used as a From address.

You do not need this for a managed *.primitive.email address: that works immediately with no DNS (see primitive-inbox).

When to reach for this

Use freely (no user confirmation needed):

• Listing domains and their verification state.
• Generating the DNS records or a zone file for the user to publish.
• Running verify or check-domain-dns to see what is missing.

Ask the user first:

• Claiming a domain (domains add): confirm the exact domain, and whether it already receives mail elsewhere.
• Anything that changes where the domain's mail goes. Publishing Primitive's MX records moves inbound mail for the whole domain to Primitive. If the domain already uses Google Workspace, Microsoft 365, or another mailbox provider, say so plainly and get an explicit yes. Consider a subdomain (mail.acme.com, agents.acme.com) instead.
• Deleting a domain or setting --no-is-active.