Check and Verify Domain DNS Status
Run a fresh DNS check, read each status, and use View Conflicts to find the exact MX, SPF, DKIM, DMARC, or CNAME mismatch.
Article details
Type, difficulty, plans, and last updated info.
▼
Article details
Type, difficulty, plans, and last updated info.
- Type
- Reference
- Difficulty
- Beginner
- Plans
- Nano · Starter · Pro · Agency
- Last updated
- Sep 9, 2026
TrekMail shows the last DNS-check result for a domain. It checks more than record presence: the relevant records must match the values needed for the selected domain setup.
Who this is for
- Users staring at a "DNS Error" or "Pending" status.
- Admins confirming their setup is live.
How verification works
When you click Verify DNS on the domain page:
- Queued check: TrekMail schedules a DNS check. If one is already running, wait for that result instead of starting several checks.
- Comparison: We compare what we find against what is required.
- Strict Match: MX priority, DKIM, and CNAMEs must be exact.
- Partial Match: SPF needs only to contain our include.
- DKIM availability: A new domain may show a DKIM value as it is being provisioned. Copy the host and value only after the dashboard displays them.
Verify DNS starts a fresh TrekMail check, but it cannot bypass caches at your DNS provider or at public resolvers. If a saved change is not visible yet, keep the correct record in place and wait for DNS caches to update instead of repeatedly changing it.
Tip: Seeing a lot of red x's? Launch the Guided Tour on the DNS Health Page (click your domain -> DNS & Health) for an interactive explanation of each record type and how to fix it.
Understanding Statuses
Domain Status (Top Level)
- ⏳ Pending DNS: TrekMail has not yet confirmed all required records. You can still create a mailbox, but do not rely on normal delivery until the domain is active.
- ✅ Active: The required records for the domain's selected setup have passed validation.
- ⚠️ Active (Warnings): Essential records are good, but Deliverability records (TLSRPT, MTA-STS) are missing or conflicting. You can still send email.
- ❌ DNS Error: A required record is missing or does not match. Review the affected row before changing DNS.
Automatic Activation
Domains transition from Pending DNS to Active automatically when both conditions are met:
- DNS records verified: All required records (MX, SPF, DKIM, DMARC) pass validation.
- DKIM key provisioned: Your unique signing key has been generated and is ready.
You do not need to manually activate a domain. Once DNS propagates and DKIM is ready, the status updates on its own. Bulk-imported domains are checked asynchronously in the background; use the status shown for each domain rather than assuming a fixed completion time.
A domain set to keep its incoming mail with another provider is judged on SPF, DKIM and DMARC only. It reaches Active without an MX record pointing here, and it sends but does not receive. See Send From a Domain You Do Not Host.
Record Status (Table Rows)
- ✅ Green Check: Perfect match.
- ⚠️ Yellow Warning: Functional, but maybe missing optimal settings (e.g., DMARC is
none). - ❌ Red Error: Critical mismatch or missing record.
"View Conflicts"
If we see a record that looks almost right but isn't, a View Conflicts button will appear. Click it to see a side-by-side comparison:
- Expected: What TrekMail wants.
- Found: What your DNS provider is sending.
- Common Fix: Usually this reveals typos or legacy records from a previous provider.
Common mistakes & quick fixes
- Symptom: "DNS Lookup Failed" message.
- Likely Cause: A temporary lookup problem or DNS that is still being published.
- Fix: Check the record values at the DNS provider, wait for the existing check to finish, then run one new check.
- Symptom: Status is Active but I can't send.
- Likely Cause: You might be on the Nano plan without BYO SMTP configured.
- Fix: Open Domains, select the domain, and check its SMTP tab.
- Symptom: DKIM keeps failing.
- Likely Cause: Your DNS provider might be splitting the long key into two strings.
- Fix: Check your DNS provider's docs on how to handle 2048-bit TXT records.
Related articles
Jump to nearby guides that continue the workflow.