Integrations
Spaceship
Connect Spaceship so Dun can see your domains and propose DNS changes in plain English. Every record write is shown as a diff and waits for your approval.
Note
How to connect
Connect once from Integrations → Spaceship, then toggle on the products you want Dun to manage.
Step 1
Step 2
Step 3
Where to get credentials: https://www.spaceship.com/application/api-manager/
What Dun can do
Each product below is something you can turn on. The examples are real prompts you can type in a chat thread.
Domains
List domains registered in the connected Spaceship account.
Which domains do I have at Spaceship?
When does example.com expire?| Permission | Required | What it does |
|---|---|---|
| List registered domains | Yes | Discover which domains live in this Spaceship account. |
DNS records
Inspect and apply approved DNS record changes via the Spaceship API.
Point app.example.com to 76.76.21.21
Add a TXT record on example.com for my Google site verification
Change the MX records on example.com to Google WorkspaceIn a playbook, bind dns.write-record to run this as a step.
| Permission | Required | What it does |
|---|---|---|
| Read existing DNS records | Yes | View record sets so Dun can suggest safe changes. |
| Apply approved DNS changes | Yes | Apex routing, CNAMEs, MX records — every write needs a chat approval. |
Troubleshooting
"Authentication failed"
Cause: The API key/token was revoked or the IP allow-list at Spaceship doesn't include Dun's egress IP.
Fix: Regenerate the key in Spaceship, and if Spaceship enforces IP allow-listing, add Dun's egress IP (Settings → Providers shows it) before saving.
"Record already exists"
Cause: A conflicting record (same name + type) is already present.
Fix: Ask Dun to update the existing record instead of adding a new one — it will show the before/after diff.