Repliqo Docs

Domain and DNS troubleshooting

Diagnose pending custom-domain verification, conflicting MX records, host formatting, propagation, and reconnection states.

Start on the affected domain's DNS records tab. Repliqo shows the generated record set, provider status, the last check time, and Verify domain or Re-check DNS.

Use the current generated values

Do not substitute values from another domain, an old screenshot, or a generic email-provider guide. Repliqo's displayed records are the source of truth for this domain.

Diagnose the symptom

SymptomWhat to check
Domain remains Pending DNSEvery record exists with the same type, host, value, and MX priority; then wait for the record TTL and verify again
Provider preview duplicates the domainEnter the host relative to the provider's managed zone instead of pasting the full hostname
Apex record is rejectedUse the provider's root convention, commonly @ or a blank name field
MX is present but failsConfirm both the target and priority; some providers put priority in a separate field
CNAME never verifies behind CloudflareSet it to DNS only, not proxied
Automatic setup returned an errorRetry once, then add the displayed records manually
Status says the domain must be re-addedRemove it, add the hostname again, and use the newly generated records
Hostname is already registeredCheck other Repliqo workspaces and confirm it was removed from any previous email service

Check relative and full hostnames

Suppose the provider manages acme.com and Repliqo displays a record for send.inbox.acme.com:

  • A provider that wants a full hostname receives send.inbox.acme.com.
  • A provider that automatically appends acme.com receives send.inbox.

After saving, inspect the provider's rendered record name. It must resolve to the hostname shown by Repliqo exactly once.

Protect existing MX routing

An MX record controls where inbound mail for that hostname is delivered.

  • Connecting inbox.acme.com changes routing for addresses under that subdomain.
  • Connecting acme.com changes routing for root addresses such as person@acme.com.

If Google Workspace or Microsoft 365 already receives root-domain mail, do not replace those MX records unless migrating all root mail intentionally. Remove an accidental root-domain setup, restore the original MX records, and add a dedicated subdomain instead.

Account for DNS propagation

DNS updates are not visible everywhere immediately. Check the TTL shown at your provider, wait at least that long after the final edit, and then select Verify domain again. Repeated edits restart the effective wait for caches that observed an earlier value.

You can also use Repliqo's public email DNS checker to inspect common email records independently of the workspace verification flow.

Verification succeeded but no mail arrives

Verification only authorizes the hostname. Open the domain's Overview tab and create an inbox address such as support@inbox.acme.com. Confirm the exact address is enabled and visible in the sidebar before sending a test message.

Automatic setup is missing

The provider-specific button appears only when Repliqo can discover a supported DNS provider and its Repliqo template. Its absence is not an error. Complete the manual record table instead.

What to collect for support

Provide:

  • The hostname and Repliqo workspace name.
  • The record type and provider status that still fails.
  • The DNS provider's rendered host, value, priority, and TTL.
  • The domain's Last checked time and the exact error shown.

Do not send account passwords, OAuth tokens, API keys, or private signing keys.

Success looks like

The domain shows Verified, its required records show successful statuses, and a created inbox receives a new external test message.

Next steps

Last updated on

On this page