dunops.com/Docsbeta

Integrations

Name.com

Connect Name.com 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 Name.com resources until you approve it.

How to connect

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

1

Step 1

Sign in to Name.com and open Account → API for Account.
2

Step 2

Create an API token (use the production API, not the test sandbox).
3

Step 3

Enter your Name.com username and paste the token below.

Where to get credentials: https://www.name.com/account/settings/api

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.

Name.com account

Name.com's v4 API lets DunOps list your domains, preview existing DNS records, and apply approved DNS changes. Connect with your Name.com username and an API token.

Type in a chat thread
Show me my Name.com name.com 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 Name.com?
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 Name.com doesn't include Dun's egress IP.

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