Prerequisites
- Set Up Your Sending Domain — The dashboard exists once a domain is configured
Verify Your DNS Records
Two questions per record, and only one of them is yours to answer.
Before You Begin
Once a sending domain is configured, Communication > Email > Senders shows the DNS Verification dashboard: a card for each record, each with its hostname and value and its own Verify.
The important idea on this screen is that each of DKIM, SPF and Return Path has two states, not one. Published in DNS means Zyntro looked the record up and found it. Accepted for sending means the delivery service has checked it and agreed. Only the second allows mail to go out, and the two can disagree for hours.
Steps
Read both lines on each card
The DKIM, SPF and Return Path cards each show two lines. A tick against Published in DNS means your DNS work is done. A tick against Accepted for sending means the record is doing its job.
The large icon at the top of the card follows acceptance, because that is the state that matters for sending.
Use a card's own Verify to confirm what you published
Verify on a single card checks live DNS immediately. Use it after creating or editing a record, to confirm you entered it correctly.
This updates Published in DNS only. A successful check here does not mean the record has been accepted, and the message on screen says so.
Use Verify All Records to ask for acceptance
Verify All Records, at the top of the page, asks the delivery service to re-check DKIM, SPF and Return Path and accept them. This is the action that moves a record from published to usable.
When it finishes, a message reports how many of the three were accepted. Sending stays blocked until all three are.
Check MX and DMARC separately
The MX and DMARC cards show a single status each, because the delivery service does not track either. Zyntro verifies both against live DNS, so their own Verify is the only check they need, and Verify All Records does not include them.
Allow for propagation
A record you have just created may not be visible yet. DNS changes usually appear within minutes but can take up to 24 hours.
If a check fails on a record you are confident about, wait and run it again rather than editing a record that was already correct.
Re-verify DKIM if it stops working
DKIM keys can be rotated, which means the record your domain needs can change. Selecting Verify on the DKIM card re-reads the current record before checking DNS, so the hostname and value on the card update to what you now need to publish.
If they have changed, publish the new values and verify again.
Result
Every card shows a green tick, and on DKIM, SPF and Return Path both lines are ticked. Your domain is published correctly and accepted for sending.
Nothing here needs routine attention. Come back when you change DNS, when DKIM is rotated, or when mail stops being delivered and you want to rule out the records as the cause.
Troubleshooting
Expected, and usually temporary. Your record is correct; the delivery service has not yet accepted it. Select Verify All Records. If it still does not accept, the record may have been published too recently — wait and try again.
Read each card to see which one is short. A record that is not published cannot be accepted, so fix publication first: use that card's own Verify to confirm what is in DNS.
Something changed in DNS. The usual causes are an edited or deleted record, a DNS host migration, or a rotated DKIM key. Select Verify on that card and compare the hostname and value shown against what your DNS host now holds.
The records are no longer the problem, so look at the mail itself. Check that recipients are not suppressed by a previous bounce or opt-out, and check your email analytics for what happened to recent sends.
