Domain verification fails because of multiple MX records
The most common reason a domain won't verify — or verifies but mail still lands somewhere else. It happens when an old mail provider's MX record is still in place alongside SyncGaze's.
What you'll see
- Clicking Verify on the domain returns “Domain verification failed”, even though you added the SyncGaze MX record.
- Or the domain shows Verified, but new email never arrives in SyncGaze — it's still going to your old provider.
Why it happens
Email delivery follows MX records by priority — the lowest priority number wins. SyncGaze only accepts a domain as correctly configured when its MX is present and no other mail server is sitting at the same or a better (lower) priority. If a record like aspmx.l.google.com (Google) or an old host is still there at priority 1 while SyncGaze is at 10, the other server keeps receiving your mail.
The tell-tale signYour domain's DNS lists two or more MX records pointing at different providers. That's the conflict to remove.
The fix
Leave only SyncGaze's MX record(s) on the domain. Here's a before / after.
Before — conflicting (won't verify)
After — correct
- Sign in to your DNS provider (where you bought the domain, or Cloudflare if you use it).
- Open the DNS records for the domain and find every MX record.
- Delete any MX that doesn't point to
mail.syncgaze.inormx.syncgaze.in. - Make sure the SyncGaze MX is present (priority doesn't matter once it's the only one).
- Save, wait 5–30 minutes for DNS to update, then return to the dashboard and click Verify.
Two SyncGaze records is fineIf your DNS shows both mail.syncgaze.in and mx.syncgaze.in, leave them — they're both ours and don't conflict with each other. The problem is only other providers' records.
Related problems
| Symptom | Cause | Fix |
|---|---|---|
| SPF “duplicate record” / mail marked as spam | Two v=spf1 TXT records exist — DNS only allows one. | Merge them into a single SPF record that includes include:syncgaze.in, and delete the extras. |
| Verify still fails after editing DNS | Changes haven't propagated yet. | Wait up to 30 minutes and click Re-check. Public DNS (Google, Cloudflare) can lag. |
| Mail sends but doesn't arrive at SyncGaze | MX correct but an old catch-all/forward is still active at the old host. | Remove forwarding at the previous provider, or cancel that account once migration is done. |
Still stuck?