# DreamHost

> Publish the SPF, DKIM, and DMARC records SendPing generates for your domain using the DreamHost panel’s DNS editor.

This guide walks through adding the DNS records SendPing generates for a domain using **DreamHost**. First add your domain in SendPing to generate the records — see [Managing domains](https://www.sendping.co/docs/domains/managing) — and keep the [DNS records](https://www.sendping.co/docs/domains/dns) reference open, since the exact values (your DKIM record and your region) come from there.

It is best practice to use a [subdomain](https://www.sendping.co/docs/kb/subdomain-vs-root) (e.g. `updates.example.com`) instead of the root domain (`example.com`). A subdomain isolates sending reputation by purpose (marketing, transactional) and keeps it separate from your corporate mail.

## Log in to DreamHost

1. **Open your website** — Log in to the **DreamHost panel** at panel.dreamhost.com and go to **Websites → Manage Websites**.
2. **Manage the domain** — Click **Manage** on the domain you want to send mail from, then open the **DNS** tab. This is where you add the records below with **Add Record**.
3. **Add each record** — Add every entry below — the DKIM TXT record, the SPF MX and TXT, and the DMARC TXT.

> **Warning:** DreamHost’s **Host** field expects only the subdomain part (e.g. `sendping._domainkey`, `send`, `_dmarc`) — do not include your full domain. Entering the full hostname produces a doubled name like `send.example.com.example.com`.

## DKIM — TXT

Add **one** TXT record holding your domain’s DKIM public key. Enter only the host prefix in **Host** — DreamHost appends your domain. Copy the value from your domain configuration page in SendPing.

**DKIM — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT Record | No | A single DKIM key record. |
| `Host` | sendping._domainkey | No | DreamHost appends `.example.com`, giving `sendping._domainkey.example.com`. `sendping` is the fixed selector SendPing uses. |
| `Points to` | v=DKIM1; k=rsa; p=<public key> | No | The DKIM key record holding your domain’s public key. |
| `TTL` | Default | No | Use the DreamHost default. |

## SPF — MX on send.example.com

SendPing uses the custom MAIL FROM subdomain `send.example.com`, which needs both an MX and a TXT record. On DreamHost the cleanest way to host an MX on a subdomain is to create the subdomain first (return to **Manage Websites → Add Website**, add `send.example.com`), then **Manage** it, choose **Add Record → MX → Manage Custom MX**, and paste the SendPing MX value.

**SPF — MX**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | MX Record | No | Routes bounce and complaint feedback for the MAIL FROM subdomain. |
| `Host` | send | No | Resolves to `send.example.com`. |
| `Points to` | feedback-smtp.us-east-1.amazonses.com | No | Region-specific feedback host. Replace `us-east-1` with your domain’s region. |
| `Priority` | 10 | No | Copy the priority shown in SendPing. Check any existing MX on this host before editing. |
| `TTL` | Default | No | DreamHost default. |

## SPF — TXT on send.example.com

**SPF — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT Record | No | SPF policy for the MAIL FROM subdomain. |
| `Host` | send | No | Same host as the MX — resolves to `send.example.com`. |
| `TXT Value` | v=spf1 include:amazonses.com ~all | No | Authorizes Amazon SES to send for the MAIL FROM subdomain. |
| `TTL` | Default | No | DreamHost default. |

## DMARC — TXT on _dmarc.example.com

**DMARC — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT Record | No | DMARC policy record. |
| `Host` | _dmarc | No | Resolves to `_dmarc.example.com`. |
| `TXT Value` | v=DMARC1; p=none; | No | A monitoring policy to start with; tighten to `quarantine` or `reject` later. See [Implementing DMARC](https://www.sendping.co/docs/kb/dmarc). |
| `TTL` | Default | No | DreamHost default. |

> **Note:** DreamHost gotchas: use only the **Host** prefix (`send`, `_dmarc`, `sendping._domainkey`), never the full domain; review [MX conflicts](https://www.sendping.co/docs/kb/mx-conflicts) if the target host is already in use; and DNS updates at DreamHost can take several hours to propagate.

Once all records shown in your SendPing domain configuration are saved, return to SendPing and [re-verify the domain](https://www.sendping.co/docs/api/domains-verify). If it stays pending, see [What if my domain isn’t verifying?](https://www.sendping.co/docs/kb/domain-not-verifying).