Get started
Solutions & troubleshooting

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

  • After you click Verify, the domain stays Pending and its card shows Conflicting DNS records found, naming the other mail server and its priority.
  • Or the domain shows Verified, but new email never arrives in SyncGaze: it's still going to your old provider.
dashboard.syncgaze.in/domains
A conflicting MX record warning
Screenshot coming soon screens/dashboard-domain-conflict.png

Domains, on the domain's card.

  1. 1Conflicting DNS records found: names the other provider's mail server and its priority. Delete that record at your registrar.
  2. 2Pending: the domain won't verify until the conflict is gone.

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.

dashboard.syncgaze.in/domains
A domain still pending after Verify
Screenshot coming soon screens/dashboard-domain-verify-failed.png

The domain card while verification is incomplete.

  1. 1Pending: SyncGaze hasn't confirmed all the records yet.
  2. 2Current step: the first record SyncGaze couldn't confirm.
  3. 3Verify: checks again once you've fixed the record.
  4. 4Mail Exchange Record: SyncGaze's MX, which must be the only one.

The fix

Leave only SyncGaze's MX record(s) on the domain. Here's a before / after.

Before: conflicting (won't verify)

northwind.com. MX 1 aspmx.l.google.com. ← remove northwind.com. MX 5 alt1.aspmx.l.google.com. ← remove northwind.com. MX 10 mail.syncgaze.in.

After: correct

northwind.com. MX 10 mail.syncgaze.in.
  1. Sign in to your DNS provider (where you bought the domain, or Cloudflare if you use it).
  2. Open the DNS records for the domain and find every MX record.
  3. Delete any MX that doesn't point to mail.syncgaze.in or mx.syncgaze.in.
  4. Make sure the SyncGaze MX is present (priority doesn't matter once it's the only one).
  5. Save, wait 5 to 30 minutes for DNS to update, then return to the dashboard and click Verify.

The value to keep is on your domain's card in the dashboard, under Mail Exchange Record.

dashboard.syncgaze.in/domains
The SyncGaze MX record to keep
Screenshot coming soon screens/dashboard-domain-dns.png

Domains, on the domain's card.

  1. 1Status: changes to Verified once only SyncGaze's MX remains.
  2. 2Verify: click after saving your DNS changes.
  3. 3Ownership (TXT): leave this record in place.
  4. 4Mail exchange (MX): the only MX your domain should have.

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.

After fixing DNS, check Reporting → Deliverability: SPF and MX should both show a green tick.

dashboard.syncgaze.in/deliverability
Deliverability checks for a domain
Screenshot coming soon screens/dashboard-deliverability.png

Reporting, then Deliverability.

  1. 1Score: reaches 100 when all four records are right.
  2. 2SPF: one record only; two SPF records fail.
  3. 3DKIM: signs your outgoing mail.
  4. 4DMARC: your policy for mail that fails checks.
  5. 5MX: found once SyncGaze's MX is in place.
SymptomCauseFix
SPF “duplicate record” / mail marked as spamTwo v=spf1 TXT records exist: DNS only allows one.Merge them into one SPF record using the value shown on your domain page, and delete the extras.
Verify still fails after editing DNSChanges haven't propagated yet.Wait up to 30 minutes and click Verify. Public DNS (Google, Cloudflare) can lag.
Mail sends but doesn't arrive at SyncGazeMX 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.