dunops.com/Docsbeta

Integrations

NameSilo

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

How to connect

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

1

Step 1

Sign in to NameSilo and open Account → API Manager.
2

Step 2

Enable API access if it is not already active, then copy your API key.
3

Step 3

Paste the key below and click Connect.

Where to get credentials: https://www.namesilo.com/account/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.

NameSilo account

NameSilo's API lets DunOps list your domains, preview existing DNS records, and apply approved DNS changes. Connect with a NameSilo API key.

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

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