Add DNS records at your provider

When you add a domain, Vaartix gives you six DNS records. This guide shows where to enter them at the most common providers. The example uses acme.in; your DKIM names and values will be different, so copy them from your domain’s page or the API response.

Type	Name (host)	Value	Priority
CNAME	abc123._domainkey	abc123.dkim.amazonses.com
CNAME	def456._domainkey	def456.dkim.amazonses.com
CNAME	ghi789._domainkey	ghi789.dkim.amazonses.com
MX	send	feedback-smtp.ap-south-1.amazonses.com	10
TXT	send	v=spf1 include:amazonses.com ~all
TXT	_dmarc	v=DMARC1; p=none;

Which provider do I use?

Your DNS provider is wherever your domain’s nameservers point, which isn’t always where you bought the domain. Look it up with dig NS acme.in +short or any online “NS lookup” tool. If the answer ends in cloudflare.com, use the Cloudflare steps even if you bought the domain at GoDaddy.

Enter only the host part

Most providers add your domain to the name automatically. In the Name or Host field, type only the part before your domain: abc123._domainkey, send or _dmarc. If you type the full abc123._domainkey.acme.in, many providers save it as abc123._domainkey.acme.in.acme.in and verification fails.

Provider steps

GoDaddy

1. Sign in, open My Products, find your domain and choose DNS (or Manage DNS).
2. Choose Add New Record for each of the six records.
3. For the three CNAME records, put abc123._domainkey in Name and abc123.dkim.amazonses.com in Value. Leave TTL at the default.
4. For the MX record, enter Name send, Value feedback-smtp.ap-south-1.amazonses.com and Priority 10.
5. For the two TXT records, enter Name send and _dmarc with the values from the table.
6. Save. GoDaddy usually publishes changes within a few minutes.

GoDaddy sometimes adds a _dmarc record of its own. If one exists already, keep it and skip ours.

Hostinger

1. In hPanel, open Domains, choose your domain, then DNS / Nameservers.
2. Under Manage DNS records, pick the Type, then fill Name and Points to (or Target, Content, depending on the record type).
3. Add the three CNAME records with names like abc123._domainkey.
4. Add the MX record: Name send, Mail server feedback-smtp.ap-south-1.amazonses.com, Priority 10.
5. Add the two TXT records for send and _dmarc.

If your domain uses Hostinger email, don’t touch the existing MX records on @. The send MX record is separate and doesn’t affect your inbox.

Cloudflare

1. In the Cloudflare dashboard, open your domain, then DNS → Records → Add record.
2. Add the three CNAME records. Set Proxy status to DNS only (grey cloud) on each one.
3. Add the MX record: Name send, Mail server feedback-smtp.ap-south-1.amazonses.com, Priority 10.
4. Add the two TXT records for send and _dmarc.

Caution

Proxied (orange cloud) DKIM records never verify, because Cloudflare answers with its own IP addresses instead of the CNAME target. Always choose DNS only for these records.

BigRock

1. Sign in to BigRock, open Domains (or Manage Orders → List/Search Orders) and choose your domain.
2. Open DNS Management (or Manage DNS). It has a tab for each record type.
3. On the CNAME Records tab, add the three DKIM records: Host Name abc123._domainkey, Value abc123.dkim.amazonses.com.
4. On the MX Records tab, add Zone send, Value feedback-smtp.ap-south-1.amazonses.com, Priority 10.
5. On the TXT Records tab, add send and _dmarc with the values from the table.

BigRock’s DNS manager only works when the domain uses BigRock’s own nameservers. If it uses Cloudflare or another provider’s nameservers, add the records there instead.

Namecheap

1. Open Domain List, choose Manage next to your domain, then the Advanced DNS tab.
2. Choose Add new record for the three CNAME records, with Host abc123._domainkey.
3. Add the two TXT records with Host send and _dmarc.
4. For the MX record, find Mail Settings on the same tab. If it isn’t set to Custom MX, switch it, then add Host send, Value feedback-smtp.ap-south-1.amazonses.com, Priority 10.

Switching Mail Settings to Custom MX removes Namecheap’s email forwarding records. If you use forwarding or Private Email, add their MX records back for @ as well.

Route 53

1. In the AWS console, open Route 53 → Hosted zones and choose your domain.
2. Choose Create record and switch to Quick create if asked.
3. CNAME records: Record name abc123._domainkey, Value abc123.dkim.amazonses.com.
4. MX record: Record name send, Value 10 feedback-smtp.ap-south-1.amazonses.com. Route 53 takes the priority as part of the value.
5. TXT records: Record name send and _dmarc. Wrap each value in double quotes, for example "v=spf1 include:amazonses.com ~all".

Check your records

DNS changes usually appear within minutes, but can take up to a few hours. Check from a terminal:

dig +short CNAME abc123._domainkey.acme.in   # abc123.dkim.amazonses.com.
dig +short MX send.acme.in                   # 10 feedback-smtp.ap-south-1.amazonses.com.
dig +short TXT send.acme.in                  # "v=spf1 include:amazonses.com ~all"
dig +short TXT _dmarc.acme.in                # "v=DMARC1; p=none;"

On Windows, use nslookup -type=CNAME abc123._domainkey.acme.in. Once the records answer correctly, call POST /domains/{id}/verify or wait for the automatic check, which runs every 10 minutes.

Common mistakes

• Domain added twice to the name: see Enter only the host part.
• Cloudflare proxy turned on for the DKIM CNAMEs: switch them to DNS only.
• Two SPF records on the same name: the send SPF record is new. Don’t merge it with the SPF record on your main domain, and don’t add a second SPF record on send.
• Spaces or quotes copied by mistake: paste values exactly, without spaces at the start or end.
• Records added at the wrong provider: check your nameservers, as shown at the top of this page.