DNS Records & Domain Verification #

Before sending or receiving mail on a custom domain (<your-domain>), you must prove domain ownership via TXT challenge (ADR-0047) and publish email authentication records (MX, SPF, DKIM, DMARC).

1. Domain Ownership Verification (_tsubame-verify) #

  1. Register the domain in https://console.<your-domain> (calls POST /v1/domains with {"tenant": "<tenant-id>", "name": "<your-domain>"}).
  2. Fetch the verification token (GET /v1/domains/challenge?tenant=<tenant-id>&domain=<your-domain>).
  3. Publish the DNS TXT record at _tsubame-verify.<your-domain>:
TypeHost / NameValueTTL
TXT_tsubame-verify.<your-domain><64-hex-verification-token>300
  1. Trigger verification (POST /v1/domains/verify with {"tenant": "<tenant-id>", "domain": "<your-domain>"}). - Challenge tokens have a default 7-day TTL (DefaultChallengeTTL) from registration. - Once verified, the domain state transitions terminally to verified.

2. Mail Routing & Authentication Records #

RecordHost / NameValue / TargetPurpose
MX@ (<your-domain>)10 mail.<your-mail-host>Routes inbound SMTP (port 25) to smtp-in
TXT (SPF)@ (<your-domain>)v=spf1 mx include:<your-spf-host> -allAuthorizes outbound mta-out / relay servers
TXT (DKIM)<selector>._domainkey.<your-domain>v=DKIM1; k=rsa; p=<YOUR_PUBLIC_DKIM_KEY>Cryptographic RSA/Ed25519 signature verification
TXT (DMARC)_dmarc.<your-domain>v=DMARC1; p=quarantine; rua=mailto:dmarc@<your-domain>Policy alignment & aggregate reporting
WARNING

smtp-in enforces inbound DMARC p=reject (ADR-0019): unaligned messages failing both SPF and DKIM are rejected with 550 5.7.1. Ensure your own SPF and DKIM records are valid before setting p=reject on your domain.

3. Verifying DNS Propagation Locally #

bash
dig +short TXT _tsubame-verify.<your-domain>
dig +short MX <your-domain>
dig +short TXT <selector>._domainkey.<your-domain>
dig +short TXT _dmarc.<your-domain>