dunops.com/Docsbeta

Integrations

IONOS

Connect IONOS 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.

Connect with an API tokenDomains1 product

Note

Every mutating action — a deploy, a scale, a secret rotation, a DNS change — surfaces a plan in chat first. Dun never touches your IONOS resources until you approve it.

How to connect

Connect once from Integrations IONOS, then toggle on the products you want Dun to manage.

1

Step 1

Sign in to the IONOS Developer portal and open DNS → API keys.
2

Step 2

Create a key — IONOS shows a public prefix and a secret.
3

Step 3

Paste the full key as {prefix}.{secret} below.

Where to get credentials: https://developer.hosting.ionos.com/keys

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.

IONOS account

IONOS' DNS API lets DunOps list your DNS zones, preview existing records, and apply approved DNS changes. Connect with an IONOS DNS API key.

Type in a chat thread
Show me my IONOS ionos account
PermissionRequiredWhat it does
Read registered domainsYesDiscover which domains live in your account.
Read existing DNS recordsYesView record sets so Dun can suggest safe changes.
Apply approved DNS changesYesApex routing, CNAMEs, MX records — every write needs a chat approval.
Receive DNS / domain webhooksOptionalInbound events only — surface registrar changes in the activity feed.

More examples

Domains

chat
Which domains do I have at IONOS?
When does example.com expire?

DNS

chat
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 Workspace

Troubleshooting

"Authentication failed"

Cause: The API key/token was revoked or the IP allow-list at IONOS doesn't include Dun's egress IP.

Fix: Regenerate the key in IONOS, and if IONOS 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.

Next steps