---
name: saasco-dns
description: "Adds the DNS records a Saasco tool returned (email SPF, DKIM, tracking, and MX rows, short-link domains, help-center domains). Writes them through the DNS host's tools when those tools are connected. Otherwise walks the user through adding them. Use when a domain, short-link, or help-center tool returned records to add."
---
# Add DNS records

This skill is the DNS step. The tool that sent you here already fetched the records. Write those rows at the host that serves this hostname. Do not invent records.

Email rows are `emailConfig.records` from `domains_getDomain`, or `records` from `domains_getReceivingConfig`. Each has `name`, `type`, `value`, `priority`, and `ttl`. `record` says what the row is for: SPF and DKIM are sending, Tracking is open and click links, Receiving is inbound mail.

Shortlink and help-center rows are a different shape. Shortlinks are `vercelVerificationDNS` on the domain `domains_enableShortlink` returns. Help-center rows are `customDomainVerificationDNS` on the help center. Each has `domain`, `type`, and `value`. `domain` is the hostname that row is for.

## Write them when you can

Look through the tools you have for one that can create DNS records for this hostname. That includes Cloudflare, Vercel, Amazon Route 53, Google Cloud DNS, and any other DNS host the user has connected. If a tool can see the zone, add each row there. Do not ask which company hosts DNS when a tool already shows the zone.

On an email row, the name is often only the left-hand label (`links`, `send`) when the host appends the domain for you. If `name` or `domain` is already a full hostname, use it as shown. MX rows need the `priority`. Leave TTL at the host's default when `ttl` is `auto`. Shortlink and help-center rows have no TTL, so leave the host's default there too.

On Cloudflare, create the record as DNS only. An orange-cloud proxy breaks mail, link tracking, and short links.

When the rows are saved, call the verify tool that tool named, once. If it is still pending, say so and stop. Do not verify in a loop.

## Otherwise walk them through it

If no connected tool can write the zone, ask which company hosts DNS. Use that host's own docs:

- [Cloudflare](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/)
- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-to-add-host-records/)
- [GoDaddy](https://www.godaddy.com/help/add-a-txt-record-19232)
- [Google Cloud DNS](https://cloud.google.com/dns/docs/records)
- [Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html)
- [Vercel](https://vercel.com/docs/domains/managing-dns-records)
- [Squarespace](https://support.squarespace.com/hc/en-us/articles/360002101888)
- [Porkbun](https://kb.porkbun.com/article/68-how-to-edit-dns-records)

Any other host: add each row as a DNS record of that type. The name, TTL, and Cloudflare rules above still apply.

Tell the user the exact rows, then wait until they say the records are saved.