DNS verification for a custom domain on AliasFleet requires four DNS records: MX, SPF, DKIM and DMARC. The records are added at the registrar or DNS provider that manages the domain, then checked in AliasFleet. Once verification passes, aliases on that domain can receive mail and forward it to a destination inbox.
The domain must already exist in AliasFleet, as described in Adding a Custom Domain. Access to DNS settings is also required, at the registrar or at the DNS provider to which the domain nameservers point.
What DNS records are required?#
Four records are required for a full domain setup. The setup page lists the exact name, type and value for each record. Each value is copied exactly as shown, one record at a time.
| Record | Purpose |
|---|---|
| MX | Directs mail servers to the destination for mail addressed to the domain. Delivery depends on this record: without it, mail does not reach the domain and forwarding does not operate. |
| SPF | A TXT record that states AliasFleet is authorised to send mail on behalf of the domain. It supports deliverability of outbound mail sent from the domain. |
| DKIM | A TXT record that adds a cryptographic signature to outgoing mail. It is required for replies and outbound sending from the domain. |
| DMARC | A TXT record that states what receiving mail servers do when SPF or DKIM checks fail. It reduces the risk of mail being sent under the domain by an unauthorised sender. |
Where do I add the records?#
Records are added at the place that manages domain DNS. In most cases that is one of two places:
- The registrar the domain was bought from, such as Namecheap or GoDaddy.
- A DNS provider, if the domain nameservers point elsewhere. Cloudflare is the common case.
The DNS records or DNS management section of that provider holds the records. The layout varies by provider, but the fields are the same in each case: record type, name (or host), and value (or destination).
How do I add the records?#
- Open Domains. Open Domains in the AliasFleet dashboard and locate the domain.
- Open the setup page. Select Continue Setup for that domain. The setup page lists the four records with their exact name, type and value.
- Add each record at the provider. In the provider DNS management section, create one record at a time, copying the type, name and value exactly as shown on the setup page.
- Save each record. Confirm each record is saved at the provider before creating the next record.
- Return to the setup page. After all four records are added, return to the setup page in AliasFleet.
How do I verify the records?#
Select Verify DNS on the setup page. AliasFleet checks each record in turn.
- Records that pass show a green checkmark.
- Records that fail show red, usually with a note about what is wrong or missing.
The check can be run as many times as needed. A failed record can be corrected at the provider and rechecked without restarting the setup.
How long does verification take?#
DNS changes take from a few minutes to 48 hours to propagate. Most providers update within an hour, and Cloudflare is usually near instant. If a record was added recently, waiting before rechecking is often sufficient.
What about subdomains?#
A subdomain setup requires only the MX record. SPF, DKIM and DMARC are inherited from the verified parent domain. The setup page reflects this and shows only the MX record for a subdomain.
What if verification fails?#
The first checks are simple: confirm each record name and value was copied exactly, with no extra spaces and no missing dot at the end of a value, and confirm enough time has passed for propagation. For anything beyond that, including duplicate SPF records, proxied records at Cloudflare and subdomain record names, see DNS Not Verifying, which covers each failure mode in full. This page covers the setup path only.
For a worked example of aliases running on a custom domain, see the blog guide How to Set Up Email Aliases on a Custom Domain.