---
title: "Domain Chief"
sidebarTitle: "Domain Chief"
description: "Verify your domain on Domain Chief with Reloop."
---
> For the complete documentation index, see [llms-docs.txt](/llms-docs.txt) or the site index [llms.txt](/llms.txt). Full docs corpus: [llms-full-docs.txt](/llms-full-docs.txt). Prefer markdown URLs (append `.md`) for agent consumption. Product skill: [skill.md](/skill.md).


Domain Chief can use Reloop **Auto-populate** when nameservers match. Manual steps are always available as a fallback.

First, log in to [Reloop](https://reloop.sh/dashboard/domain) and [add a domain](/docs/guides/connect-domain/add-domain).

<DocImage
	label="Reloop — Add domain"
	src="/docs/images/docs/guides/connect-domain/shared/add-domain.png"
	alt="Add Domain dialog in Reloop"
/>

<Tip>
It is [best practice to use a subdomain](/docs/guides/connect-domain/what-is-a-domain) (for example `mail.example.com` or `team.example.com`) instead of the root domain (`example.com`). A subdomain keeps sending reputation separate and is especially important if you enable receiving with Reloop.
</Tip>

## Automatic setup (recommended)

The fastest way to verify your domain on Domain Chief is **Auto populate** in Reloop. This uses [Domain Connect](https://www.domainconnect.org/) — Domain Chief indexes public templates automatically ([Domain Chief Domain Connect](https://aka.chief.app/domainconnect)).

1. Go to your [Domains](https://reloop.sh/dashboard/domain) page in Reloop and open the domain.
2. (Optional) If you want to receive emails, turn **Receiving** on before Auto-populate so the inbound MX is included. [Learn more below](#receiving-emails).
3. Click **Auto populate** (shown when Reloop detects Domain Chief nameservers).
4. Authorize Reloop in Domain Chief and approve the records.
5. Return to Reloop — records are written automatically.

That’s it. Your domain will usually verify within a few minutes.

If Auto-populate fails or Reloop does not offer it, use **Manual setup** below. See also [Auto-populate DNS](/docs/guides/connect-domain/auto-populate) and [Auto-populate failed](/docs/guides/connect-domain/troubleshoot/auto-populate-failed).

## Manual setup

If you prefer to add DNS records manually, follow these steps. Always copy Type / Name / Value from your domain page in Reloop — examples below use placeholders.

### Log in to Domain Chief

Log in to [Domain Chief](https://domain.chief.app) and open DNS for the domain whose nameservers match `ns.domainchief.app` / `.eu` / `.nl` / `.net`.

Domain Chief → select domain → DNS.

If Reloop or `dig NS yourdomain.com` shows a different host, stop and edit that host instead — see [Wrong nameservers](/docs/guides/connect-domain/troubleshoot/wrong-nameservers).

### Add MX SPF record

Add a record in Domain Chief:

1. Set the Type to `MX`.
2. Set the **Name** to the host Reloop shows (for a subdomain like `team.example.com`, often `team` or `@` depending on the UI).
3. Copy the MX value from Reloop into the mail server / value field (typically `reloop.sh`).
4. Use `Auto` or the provider default for **TTL**.
5. Set **Priority** to the value Reloop shows (often `10`).
6. Save.

<DocImage
	label="Reloop — Sending MX"
	src="/docs/images/docs/guides/connect-domain/shared/spf-mx-reloop.png"
	alt="Reloop sending MX (SPF) record"
/>

| Domain Chief | Reloop | Example value |
| --- | --- | --- |
| Type | Type | `MX` |
| Name / Host | Name | `team` (or `@` for the root) |
| Value / Mail server | Value | `reloop.sh` |
| Priority | Priority | `10` |
| TTL | TTL | `Auto` |

<Info>
Omit your domain from the Name field when Domain Chief appends it. Paste `team`, not `team.example.com`.
</Info>

<Info>
Do not reuse the same priority for conflicting MX records you must keep. If Priority `10` is already in use on that host, follow Reloop’s UI or use a [separate subdomain](/docs/guides/connect-domain/what-is-a-domain).
</Info>

### Add TXT SPF record

Add a record in Domain Chief:

1. Set the Type to `TXT`.
2. Set the **Name** to the host Reloop shows (same host as the sending MX, e.g. `team` or `@`).
3. Copy the TXT value from Reloop (typically `v=spf1 include:reloop.sh -all`).
4. Use `Auto` or the provider default for **TTL**.
5. Save.

<DocImage
	label="Reloop — SPF TXT"
	src="/docs/images/docs/guides/connect-domain/shared/txt-spf-reloop.png"
	alt="Reloop SPF TXT record"
/>

| Domain Chief | Reloop | Example value |
| --- | --- | --- |
| Type | Type | `TXT` |
| Name / Host | Name | `team` (or `@` for the root) |
| Value / Content | Value | `v=spf1 include:reloop.sh -all` |
| TTL | TTL | `Auto` |

<Info>
Omit your domain from the Name field when Domain Chief appends it. Paste `team`, not `team.example.com`.
</Info>

<Warning>
Never create a second SPF TXT on the same host. If SPF already exists, merge `include:reloop.sh` into that record. See [SPF conflicts](/docs/guides/connect-domain/troubleshoot/spf-conflicts).
</Warning>

### Add TXT DKIM record

Add a record in Domain Chief:

1. Set the Type to `TXT`.
2. Set the **Name** from Reloop (selector is usually `reloop._domainkey`). Under an apex zone this may be `reloop._domainkey.team`.
3. Copy the full TXT value from Reloop into the value field (`v=DKIM1; k=rsa; p=…`).
4. Use `Auto` or the provider default for **TTL**.
5. Save.

<DocImage
	label="Reloop — DKIM TXT"
	src="/docs/images/docs/guides/connect-domain/shared/txt-dkim-reloop.png"
	alt="Reloop DKIM TXT record"
/>

| Domain Chief | Reloop | Example value |
| --- | --- | --- |
| Type | Type | `TXT` |
| Name / Host | Name | `reloop._domainkey` (or `reloop._domainkey.team` under the apex zone) |
| Value / Content | Value | `v=DKIM1; k=rsa; p=…` (unique per domain) |
| TTL | TTL | `Auto` |

<Info>
Omit your domain from the Name field when Domain Chief appends it. Paste `reloop._domainkey` or `reloop._domainkey.team`, not the full FQDN ending in `.example.com`.
</Info>

### Receiving emails

If you want Reloop to **receive** mail on this hostname, turn **Receiving** on in the domain settings in Reloop, then add an MX record in Domain Chief:

1. Set the Type to `MX`.
2. Set the **Name** to the host Reloop shows (e.g. `team` or `@`).
3. Copy the MX value from Reloop (typically `inbound.reloop.sh`).
4. Use `Auto` or the provider default for **TTL**.
5. Set **Priority** as shown in Reloop (often `10`).
6. Save.

<DocImage
	label="Reloop — Receiving MX"
	src="/docs/images/docs/guides/connect-domain/shared/mx-receive-reloop.png"
	alt="Reloop receiving MX record"
/>

| Domain Chief | Reloop | Example value |
| --- | --- | --- |
| Type | Type | `MX` |
| Name / Host | Name | `team` (or `@` for the root) |
| Value / Mail server | Value | `inbound.reloop.sh` |
| Priority | Priority | `10` |
| TTL | TTL | `Auto` |

<Warning>
When Reloop’s inbound MX is active on a hostname, Reloop receives mail for that hostname according to MX priority. That can conflict with another inbox already using MX on the same name — prefer a [subdomain](/docs/guides/connect-domain/what-is-a-domain). See [MX conflicts](/docs/guides/connect-domain/troubleshoot/mx-conflicts) and [Sending vs receiving](/docs/guides/connect-domain/sending-vs-receiving).
</Warning>

### Complete verification

Return to [Domains](https://reloop.sh/dashboard/domain) in Reloop, open the domain, and click **Verify & finish**. It may take a few minutes (rarely up to 48–72 hours) — see [propagation](/docs/guides/connect-domain/verification/propagation).

<DocImage
	label="Reloop — Verify & finish"
	src="/docs/images/docs/guides/connect-domain/shared/verify-and-finish.png"
	alt="Verify and finish domain setup in Reloop"
/>

When verification succeeds, Reloop shows **You're all set!** — Domain added → Verified → Ready to send. Your domain is verified and you are good to go.

<DocImage
	label="Reloop — You're all set"
	src="/docs/images/docs/guides/connect-domain/shared/verified-domain.png"
	alt="Verified domain ready to send in Reloop"
/>

## Domain Chief-specific notes

- Domain Chief auto-indexes public Domain Connect templates — prefer **Auto populate** when Reloop offers it.
- Auto-populate only works when public nameservers point at Domain Chief.
- Optional **DMARC** and **tracking** (`link` CNAME) rows also appear in Reloop when enabled — add them the same way from the dashboard values.

## Troubleshooting

If your domain is not successfully verified, try these common fixes.

<AccordionGroup>
  <Accordion title="Reloop does not show Auto populate">
    Confirm nameservers are Domain Chief (`dig NS yourdomain.com`). Auto-populate needs Domain Chief hosted DNS. Otherwise use manual setup above.
  </Accordion>
  <Accordion title="Verification failed after I added records">
    Re-open the Reloop domain page and compare every Type / Name / Value to Domain Chief. Fix typos, truncated DKIM keys, and duplicate SPF records. Then click **Verify** again.
  </Accordion>
  <Accordion title="It has been hours and status is still pending">
    Follow [Domain not verifying](/docs/guides/connect-domain/troubleshoot/not-verifying) and [DNS propagation](/docs/guides/connect-domain/verification/propagation).
  </Accordion>
</AccordionGroup>

## Related

- [DNS records explained](/docs/guides/connect-domain/dns-records-explained)
- [Manual DNS setup](/docs/guides/connect-domain/manual-setup)
- [Auto-populate DNS](/docs/guides/connect-domain/auto-populate)
- [All provider guides](/docs/guides/connect-domain/providers)