Reloop

Beta
Get Started

For the complete documentation index, see llms-docs.txt or the site index llms.txt. Full docs corpus: llms-full-docs.txt. Prefer the markdown version of this page at /docs/guides/connect-domain/providers/domain-chief.md. Product capabilities: skill.md. Docs MCP: /docs/mcp. Site MCP: /mcp.

Domain Chief

Verify your domain on Domain Chief with Reloop.

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

First, log in to Reloop and add a domain.

Reloop — Add domain
Add Domain dialog in Reloop

It is best practice to use a subdomain (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 use Reloop receiving (on by default for new domains).

The fastest way to verify your domain on Domain Chief is Auto populate in Reloop. This uses Domain Connect — Domain Chief indexes public templates automatically (Domain Chief Domain Connect).

  1. Go to your Domains page in Reloop and open the domain.
  2. Check Email Receiving before Auto-populate. New domains start with Receiving on, so inbound MX (inbound.reloop.sh) is usually included. Turn Email Receiving off first if this hostname must keep Google Workspace / Microsoft 365 — or use a subdomain. Learn more below.
  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 and click Verify & finish (setup) or Verify Domain (detail) to start checks.

Verification often finishes within a few minutes after DNS publishes; allow longer if resolvers are slow (propagation).

If Auto-populate fails or Reloop does not offer it, use Manual setup below. See also Auto-populate DNS and 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 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.

Add Sending MX 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.
Reloop — Sending MX
Reloop sending MX record
Domain ChiefReloopExample value
TypeTypeMX
Name / HostNameteam (or @ for the root)
Value / Mail serverValuereloop.sh
PriorityPriority10
TTLTTLAuto

Omit your domain from the Name field when Domain Chief appends it. Paste team, not team.example.com.

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.

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.
Reloop — SPF TXT
Reloop SPF TXT record
Domain ChiefReloopExample value
TypeTypeTXT
Name / HostNameteam (or @ for the root)
Value / ContentValuev=spf1 include:reloop.sh -all
TTLTTLAuto

Omit your domain from the Name field when Domain Chief appends it. Paste team, not team.example.com.

Never create a second SPF TXT on the same host. If SPF already exists, merge include:reloop.sh into that record. See SPF conflicts.

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.
Reloop — DKIM TXT
Reloop DKIM TXT record
Domain ChiefReloopExample value
TypeTypeTXT
Name / HostNamereloop._domainkey (or reloop._domainkey.team under the apex zone)
Value / ContentValuev=DKIM1; k=rsa; p=… (unique per domain)
TTLTTLAuto

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.

Receiving emails

Email Receiving is on by default for new domains. If it stays on, add the inbound MX 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.
Reloop — Receiving MX
Reloop receiving MX record
Domain ChiefReloopExample value
TypeTypeMX
Name / HostNameteam (or @ for the root)
Value / Mail serverValueinbound.reloop.sh
PriorityPriority10
TTLTTLAuto

Publishing Reloop’s inbound MX on a hostname that already has Google/Microsoft MX can divert or split delivery depending on priority. Prefer a subdomain, or turn Email Receiving off for send-only. See MX conflicts and Sending vs receiving.

Complete verification

Return to Domains in Reloop. On the setup page click Verify & finish; on the domain detail page click Verify Domain (menu: Re-verify DNS). It may take a few minutes (rarely up to 48–72 hours) — see propagation.

Reloop — Verify & finish
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.

Reloop — You're all set
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.
  • DMARC is required for verification when Email Sending is on (keep an existing policy if you already have one). Tracking CNAME is on by default for new domains — host is usually link on apex, or link.<sub> for subdomains; copy from the dashboard.

Troubleshooting

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

Was this page helpful?

Edit this page
CloudflarePreviousDreamHostNext