Start here

# Troubleshooting

Resolve domain verification and DNS setup problems.

## Cloudflare automatic setup is unavailable

Automatic setup supports Cloudflare-hosted DNS. A domain registered with Cloudflare but using another provider’s nameservers needs setup at that DNS provider. Choosing Cloudflare with **Change** updates the instructions but does not enable automatic setup.

If the option is missing or approval fails, use **Import a file** or **Add manually**. For DKIM CNAMEs, disable proxying and use **DNS only**. Returning from Cloudflare does not confirm verification: select **Check verification** in Sendy and wait for **Verified**. See [Cloudflare setup steps](https://usesendy.com/docs#cloudflare-domain-connect) for DKIM and the separate optional return-address approval.

## DKIM records not verifying

Your domain stays **Pending** and DNS queries return no DKIM CNAMEs, even days after adding them. See the [domain verification and DNS setup steps](https://usesendy.com/docs#setup-heading).

### Most common cause: doubled domain in the Host field

Registrars such as Namecheap append the domain automatically. Enter only `<token>._domainkey` in **Host**, not the full name. Replace `<token>` with a token from your domain page. The quotes in these examples keep the placeholder safe in your shell.

1.  Check whether the doubled name resolves:
    
    Bash · Check for a doubled domain
    
    ```
    dig CNAME '<token>._domainkey.example.com.example.com' +short
    ```
    
    If this returns the SES target, the Host was entered with the full domain.
2.  Edit each of the three CNAMEs so **Host** is `<token>._domainkey`, leaving **Value** unchanged.
3.  After saving the corrected records, delete any malformed records left at the doubled names.

### Other causes

*   Custom nameservers, such as Cloudflare or Route 53, mean records added at the registrar are ignored. Check where your DNS is hosted:
    
    Bash · Find authoritative nameservers
    
    ```
    dig NS example.com +short
    ```
    
*   The record type must be CNAME, not TXT or A.
*   A CNAME cannot coexist with another record at the same host.
*   Check that the Value is complete and has no stray whitespace.
*   If the verified identity is a subdomain, publish its tokens under that subdomain, not the apex. Account for the zone your DNS provider appends.
*   If the identity was deleted and recreated, replace stale tokens with the records shown on your domain page.

### Check the records properly

1.  Query an authoritative nameserver first to bypass recursive caching. This command uses the first nameserver returned for the domain:
    
    Bash · Query authoritative DNS
    
    ```
    dig @$(dig NS example.com +short | head -n 1) CNAME '<token>._domainkey.example.com' +norecurse
    ```
    
    Check the other authoritative nameservers if their answers differ.
2.  Compare with a public resolver. Repeat for each of the three tokens:
    
    Bash · Query a public resolver
    
    ```
    dig @1.1.1.1 CNAME '<token>._domainkey.example.com'
    ```
    

Read the status and answer section:

*   `NOERROR` with a CNAME answer: compare its target with the Value on your domain page.
*   `NOERROR` with no answer: the name exists, but has no CNAME record.
*   `NXDOMAIN`: the queried name does not exist.

Resolvers cache “not found” answers too. After a fix, a public resolver can still show a missing record until this negative cache expires. Wait before checking again; repeated queries do not refresh the cache.

Registrar changes usually appear within about 30 minutes, and verification often follows shortly after. If records are still missing from authoritative DNS after a few hours, check the configuration rather than waiting for propagation. If all three resolve correctly but the domain stays Pending, SES verification can take up to 72 hours.

### Namecheap note

Namecheap has no zone-file import in Advanced DNS. Add the three records individually.
