The mail-DNS checklist compares publicly visible records with the selected domain's Virtualmin mail zone. Use it when Lucid hosts your email. Creating a mailbox, connecting website DNS, or issuing a website certificate does not prove email is ready. If email stays with another provider, retain that provider's routing and authentication records.
- Open Hosting services → Manage website → Email in Control Center. Confirm the domain, then find Connect mail DNS. Email must be enabled before this checklist is available.
- Read the displayed MX, mail-address, SPF, DKIM, and DMARC values. These come from the domain's server configuration. If a required value is missing, ask support to configure it; do not invent a record or reuse another domain's key.
- For Keep my DNS provider, publish the intended records at that provider. Keep mail hostnames DNS-only when using Cloudflare. With Lucid nameservers, verify delegation and the records served by the managed zone. Choosing the DNS method does not by itself confirm public records.
- Preserve other authorized senders when updating SPF, and publish one SPF policy. Enter an MX priority separately if your provider requests it. Copy the complete DKIM value and use TTL Auto or the provider's default unless instructed otherwise. See email authentication guidance before changing an established configuration.
- Select Check mail DNS. Allow at least two minutes between requests; saved results can remain visible for up to five minutes. Read the checked time as well as each result.
- Interpret Matches as a match with the server zone. Not found means the expected record was not found; Different — review offers Show detected values for comparison. Not checked, Check unavailable, and Support review require a check, later retry, or support investigation as indicated.
Check the result: Send a message to an external mailbox and reply from it. Inspect authentication results when testing SPF/DKIM/DMARC. Matching DNS does not test SMTP delivery, reverse DNS, signing, server certificates, or sender reputation; those may need support checks. Virtualmin email troubleshooting
Common problems: An old AAAA record can route mail elsewhere. MX destinations need appropriate direct address records. A deliberate multi-provider configuration may differ from the server zone, so seek review rather than replacing correct records just to obtain a green status. Include the domain, checked time, and detected values in a support request, without passwords.
Related: Create a mailbox, SPF, DKIM, and DMARC, Delivery problems.
Leave a Reply