ZenotiHelp

Configure DNS for email delivery

ZTZenoti Docs Team Updated May 3, 2026 7 min readHow-to

To ensure reliable delivery of Zenoti email notifications — appointment confirmations, marketing campaigns, membership reminders, and other transactional emails — your organization's IT team must configure several DNS records. These records authenticate Zenoti as an authorized email sender for your domain and help prevent emails from landing in spam folders.

Before you begin

  • You must have access to your organization's DNS management console (for example, GoDaddy, Cloudflare, Route 53, or your domain registrar's DNS panel).
  • Zenoti generates the exact DNS records (with tenant-specific values) for you in-app. Navigate to Configuration > Business details > Customize outgoing email addresses to see them — you do not need to compose the records by hand or request them through a support ticket.
  • DNS changes can take 24 to 48 hours to propagate globally. Plan your configuration ahead of any scheduled email campaigns or go-live dates.

Permission: Access to your organization's external DNS management console is required. This is not a Zenoti permission.

Steps

Get your DNS records from Zenoti (in-app)

Zenoti provides an in-app wizard that generates the exact, tenant-specific DNS records you need and verifies them once they are published. Use this as your starting point.

  1. Navigate to Configuration > Business details > Customize outgoing email addresses.
  2. Under Add all these records to your DNS Host, Zenoti displays the required DNS records:
  • MX Record (CNAME)
  • DKIM1 (CNAME)
  • DKIM2 (CNAME)
  • DMARC (TXT)
  1. Zenoti generates tenant-specific CNAME hosts for your domain (for example, em3456.serenityspa.com, em4123.zenoti.com). Copy the exact Name/Host and Value/Target shown — do not substitute generic selectors.
  2. Add each record to your DNS host (see the per-record detail below).
  3. Back in Zenoti, click Verify to check whether your DNS records have been configured correctly. There are two verification statuses:
  • Missing — the DNS records have not been detected yet.
  • Enabled — the DNS records are correctly configured.

The detailed per-record steps below explain how each record works and how to add it in your DNS console.

1. Configure the SPF record

SPF (Sender Policy Framework) tells receiving mail servers which servers are authorized to send email on behalf of your domain.

  1. Sign in to your DNS management console.
  2. Locate the existing TXT record for your domain that starts with v=spf1. If no SPF record exists, create a new one.
  3. Add the Zenoti SPF include directive to the record. The final record should look similar to:

v=spf1 include:_spf.zenoti.com include: ~all

  1. Save the record.

Important: If your domain already has an SPF record, merge the Zenoti include directive into the existing record. Do not create a second SPF TXT record. DNS allows only one SPF record per domain. Multiple SPF records cause authentication failures.

2. Configure the DKIM records

DKIM (DomainKeys Identified Mail) adds a digital signature to outgoing emails, allowing receiving servers to verify that the email was not altered in transit.

  1. In your DNS management console, create new CNAME records using the selector names and values provided by Zenoti during onboarding.
  2. Zenoti typically provides two CNAME records. For each record:
  • Name/Host: The DKIM selector (for example, zenoti1._domainkey and zenoti2._domainkey).
  • Value/Target: The CNAME target provided by Zenoti.
  1. Save both CNAME records.

3. Configure the DMARC record

DMARC (Domain-based Message Authentication, Reporting, and Conformance) tells receiving servers what to do with emails that fail SPF or DKIM checks. It also enables reporting so you can monitor authentication results.

  1. In your DNS management console, create a new TXT record:
  • Name/Host: _dmarc
  • Value: Start with a monitoring-only policy:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com

  1. Save the record.
  2. After monitoring for 2 to 4 weeks and confirming that legitimate emails pass authentication, tighten the policy:
  • Quarantine: v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com
  • Reject (strictest): v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com

Tip: Start with p=none to collect data without affecting email delivery. Move to p=quarantine or p=reject only after you have verified that all legitimate email sources for your domain pass SPF and DKIM.

4. Verify domain alignment for DMARC

DMARC requires the From-header domain to be aligned (relaxed or strict) with either the SPF Return-Path domain or the DKIM signing domain. If the Zenoti-managed sending domain is not aligned with your From-header domain, DMARC fails even when SPF and DKIM individually pass.

  1. Send a test email from Zenoti and inspect the message headers in the receiving mail client.
  2. Check that the From address domain matches (relaxed alignment) or exactly equals (strict alignment) either the Return-Path domain (for SPF alignment) or the d= value in the DKIM signature (for DKIM alignment).
  3. If alignment fails, raise a support ticket so Zenoti can confirm the sender configuration for your tenant.

5. Configure BIMI (optional)

BIMI (Brand Indicators for Message Identification) lets organizations with a strong DMARC policy display their brand logo next to authenticated emails in supporting clients (Gmail, Yahoo Mail, Apple Mail). BIMI is optional and does not work until your DMARC policy is at p=quarantine or stronger.

  1. Confirm your DMARC policy is at p=quarantine or p=reject and has been monitored for several weeks with no unexpected sources.
  2. Prepare an SVG logo that meets BIMI requirements (square aspect ratio, SVG Tiny PS profile).
  3. For Gmail and Apple Mail brand indicators, obtain a Verified Mark Certificate (VMC) from an authorized issuing authority. Yahoo accepts non-VMC BIMI in many cases.
  4. Publish a TXT record at default._bimi.yourdomain.com:

v=BIMI1; l=https://yourdomain.com/path/to/logo.svg; a=https://yourdomain.com/path/to/vmc.pem

Omit the a= value if you do not have a VMC. 5. Save the record and wait for DNS propagation.

Note: Publishing a BIMI record while DMARC is at p=none has no effect. Publishing without DMARC alignment can cause supporting clients to skip the logo display silently.

6. Confirm MX record health

Outbound authentication does not depend on your MX records, but the MX configuration governs inbound bounce-handling and feedback-loop deliverability. Periodically verify your MX records are correctly published and unchanged from your mail provider's specification.

Verify your DNS configuration

After saving all records, verify that they are correctly published:

  1. Wait at least 1 hour for initial propagation (full propagation can take up to 48 hours).
  2. Use a DNS verification tool such as MXToolbox or Google Admin Toolbox:
  • SPF check: Look up the TXT record for your domain and confirm the Zenoti include directive is present.
  • DKIM check: Look up the CNAME records for the DKIM selectors and confirm they resolve to the Zenoti-provided targets.
  • DMARC check: Look up the TXT record for _dmarc.yourdomain.com and confirm the policy is published.
  • BIMI check (optional): Look up the TXT record for default._bimi.yourdomain.com and confirm the logo URL resolves.
  1. Send a test email from Zenoti (for example, a test appointment confirmation) and check the email headers for SPF, DKIM, and DMARC pass results plus alignment.

What to look for in DMARC reports

During the 2–4 week monitoring window before tightening from p=none to p=quarantine or p=reject, review your DMARC aggregate (rua) reports for:

  • Source IPs you do not recognize — investigate whether they are legitimate (forwarders, marketing tools, payroll vendors, transactional senders) or unauthorized senders. Authorize legitimate sources by adding them to your SPF record or by enabling DKIM signing for them.
  • SPF / DKIM pass rates by source — sources that pass both can be included in a tighter policy without disruption.
  • Alignment failures versus authentication failures — alignment failures usually indicate a subdomain or third-party-sender configuration issue (the email authenticated but the domains do not match). Authentication failures indicate a wrongly-configured DNS record or an unauthorized sender.
  • Volume trends — sustained spikes from unfamiliar IPs may indicate a domain-spoofing attempt and warrant immediate investigation.

Tip: Use a DMARC report-aggregation service to convert raw XML aggregate reports into a readable dashboard. Manually parsing aggregate reports does not scale beyond a few sources.

Common issues

Issue Cause Resolution
SPF authentication fails Multiple SPF TXT records on the domain Merge all SPF includes into a single TXT record.
DKIM authentication fails CNAME records not yet propagated Wait up to 48 hours and re-check. Verify the selector names match exactly.
DMARC fails despite SPF and DKIM passing Domain alignment failure Verify From-header alignment against SPF Return-Path or DKIM signing domain (see step 4).
Emails still going to spam after DNS setup DMARC policy set to p=none (monitoring only) Move to p=quarantine or p=reject after confirming legitimate emails pass checks.
DNS changes not visible TTL (Time to Live) on old records is high Lower the TTL before making changes, or wait for the current TTL to expire.
SPF record exceeds 10 DNS lookup limit Too many include directives in the SPF record Use an SPF flattening tool to reduce lookup count, or consolidate includes.
BIMI logo does not display DMARC policy is p=none, or VMC missing for clients that require one Tighten DMARC to p=quarantine or p=reject; obtain a VMC if your audience uses Gmail or Apple Mail.

Tips

  • Keep a record of the original DNS values before making changes so you can revert if needed.
  • If your organization uses multiple email service providers (for example, Google Workspace, Microsoft 365, and Zenoti), ensure all of them are included in your SPF record.
  • Review your DMARC reports regularly to identify any unauthorized email sources using your domain.
Was this article helpful?
Your feedback helps us improve our documentation.