Orbit DNS records (orbit.singlebit.xyz)
Quickest: one paste (Vercel CLI, about 10 seconds)
For whoever manages singlebit.xyz on Vercel. In a terminal logged in to Vercel (npx vercel login
if not), paste all of this. If the domain belongs to a Vercel team, add --scope <team-slug> to each
line (npx vercel teams ls shows the slug).
npx vercel dns add singlebit.xyz orbit A 44.213.142.21
npx vercel dns add singlebit.xyz 3wgk7hlnes6fv2nixxg7tn2nohhj73ml._domainkey.orbit CNAME 3wgk7hlnes6fv2nixxg7tn2nohhj73ml.dkim.amazonses.com
npx vercel dns add singlebit.xyz vnweauzoxigupxwbk6omvstqqxzoyqdw._domainkey.orbit CNAME vnweauzoxigupxwbk6omvstqqxzoyqdw.dkim.amazonses.com
npx vercel dns add singlebit.xyz muhvrpwrmzlzh7xfoisar3h27suoblmw._domainkey.orbit CNAME muhvrpwrmzlzh7xfoisar3h27suoblmw.dkim.amazonses.com
npx vercel dns add singlebit.xyz send.orbit MX feedback-smtp.us-east-1.amazonses.com 10
npx vercel dns add singlebit.xyz send.orbit TXT "v=spf1 include:amazonses.com ~all"
Each line prints the record it created. That's all.
Or by hand in the dashboard
Vercel → Domains → singlebit.xyz → DNS Records → Add, one record per row. Names are relative
to singlebit.xyz (Vercel adds the ending). TTL 60 for all.
| # | Name | Type | Value | Priority |
|---|---|---|---|---|
| 1 | orbit | A | 44.213.142.21 | |
| 2 | 3wgk7hlnes6fv2nixxg7tn2nohhj73ml._domainkey.orbit | CNAME | 3wgk7hlnes6fv2nixxg7tn2nohhj73ml.dkim.amazonses.com | |
| 3 | vnweauzoxigupxwbk6omvstqqxzoyqdw._domainkey.orbit | CNAME | vnweauzoxigupxwbk6omvstqqxzoyqdw.dkim.amazonses.com | |
| 4 | muhvrpwrmzlzh7xfoisar3h27suoblmw._domainkey.orbit | CNAME | muhvrpwrmzlzh7xfoisar3h27suoblmw.dkim.amazonses.com | |
| 5 | send.orbit | MX | feedback-smtp.us-east-1.amazonses.com | 10 |
| 6 | send.orbit | TXT | v=spf1 include:amazonses.com ~all |
What each one is for
- 1: the address
orbit.singlebit.xyz→ Orbit's server (AWS, US East). It takes priority over the existing*.singlebit.xyzwildcard to Vercel; no Vercel project usesorbit. - 2–4: DKIM signing for Orbit's email (Amazon SES). SES verifies the domain by itself once these resolve.
- 5–6: the bounce address
send.orbit.singlebit.xyz, so Orbit's mail passes SPF.
Nothing existing changes. singlebit.xyz's own records (Google Workspace mail, SPF, DMARC, CAA) stay
as they are. Its DMARC policy already covers orbit, so no DMARC record is needed.
Check
dig +short orbit.singlebit.xyz # 44.213.142.21
dig +short CNAME 3wgk7hlnes6fv2nixxg7tn2nohhj73ml._domainkey.orbit.singlebit.xyz
dig +short MX send.orbit.singlebit.xyz # 10 feedback-smtp.us-east-1.amazonses.com
dig +short TXT send.orbit.singlebit.xyz # "v=spf1 include:amazonses.com ~all"
These values come from the orbit-prod stack's outputs (created 30 October 2026). If the stack is
ever recreated, the IP and the three DKIM tokens change: read them again with
aws cloudformation describe-stacks --stack-name orbit-prod --query 'Stacks[0].Outputs' --output table