Repliqo Docs

Connect a custom domain

Add a domain, publish its generated DNS records, verify it, and create shared inbox addresses in Repliqo.

Use a custom domain when you want Repliqo to host shared addresses such as support@inbox.acme.com, sales@inbox.acme.com, or info@inbox.acme.com.

Path: Settings → Domains → Add domain

Permissions

Only workspace owners and admins can add, verify, or remove domains and create inbox addresses.

Before you add the domain

You need access to the DNS provider that manages the hostname.

Protect existing email

If your root domain already receives mail through Google Workspace, Microsoft 365, or another provider, use a dedicated subdomain such as inbox.acme.com. Connecting the root acme.com requires an inbound MX record at the root and can change where all mail for @acme.com is delivered.

Choose the root domain only when you intentionally want Repliqo to receive its inbound mail.

1. Add the hostname

  1. Open Settings → Domains.
  2. Select Add domain.
  3. Enter a hostname such as inbox.acme.com — not an email address or URL.
  4. Select Add domain.

Repliqo opens the domain detail page and retrieves the DNS records required for that hostname.

2. Publish DNS

Automatic setup, when available

If Repliqo shows Set up with provider:

  1. Select the button.
  2. Review the proposed records at your DNS provider.
  3. Approve the changes.
  4. Return to Repliqo. Verification starts automatically after the redirect.

The button appears only when Repliqo detects a provider that supports this setup. If it does not appear, or the provider flow is cancelled, use manual setup.

Manual setup

  1. Open the domain's DNS records tab.
  2. At your DNS provider, create every record shown by Repliqo.
  3. Copy the generated Type, Name / host, Value, Priority, and TTL exactly where your provider asks for them.
  4. Save the records and allow time for DNS caches to refresh.

Do not copy example targets from another domain or from this guide. Generated values can differ by domain and email-infrastructure region.

Understand the host field

DNS providers use two common formats:

Provider asks forEnter
Full hostname or FQDNThe full host displayed by Repliqo
Name relative to the managed zoneRemove only the zone suffix the provider automatically appends
Root or apex@ when the provider uses that convention

Check the provider's preview before saving. A result such as send.inbox.acme.com.acme.com means the zone suffix was appended twice.

If a provider offers proxying for a CNAME record, use DNS only for email records. MX and TXT records are not proxyable.

3. Verify the domain

Return to Repliqo and select Verify domain. A pending result usually means DNS has not propagated yet or at least one record does not match.

Verification makes the hostname eligible for inbox addresses; it does not create an address or begin routing mail by itself.

4. Create an inbox address

  1. After the domain shows Verified, open its Overview tab.
  2. Select Create inbox.
  3. Enter the local part, such as support, plus the inbox and sender names.
  4. Create the inbox.

Mail to the new address can now route into its Repliqo queue.

Success looks like

  • The domain status is Verified.
  • Required DNS records show a successful provider status.
  • At least one address, such as support@inbox.acme.com, appears under Inboxes on this domain.
  • A test message to the address appears in Repliqo and a reply sends from it.

Common problems

  • Pending DNS: compare each generated field with the live provider record and wait for its TTL to expire.
  • Existing mail stopped: review the root-domain warning and restore the previous MX records if the root was connected unintentionally.
  • Automatic setup did not finish: return to the DNS tab and use the manual records.
  • Domain needs to be re-added: remove it, add the same hostname again, and publish the newly generated records.
  • Hostname is already registered: it may belong to another Repliqo workspace or still exist at the underlying email provider.

See domain troubleshooting for a symptom-by-symptom checklist.

Next steps

Last updated on

On this page