Start with the direction of the message
An email domain has two distinct jobs: receiving messages addressed to it and supporting messages sent using its name. The DNS records for those jobs overlap less than many people expect. A domain can send mail without hosting an inbox, and a domain can receive mail even if nobody sends from it.
When someone emails a person at example.com, the sender’s mail server needs to find the system that accepts mail for example.com. When someone sends a message that appears to be from example.com, the recipient’s system may instead look up records that help it assess whether the sending system is authorized and whether the message is authentic. Separating those questions makes email DNS easier to plan and troubleshoot.
Receiving mail: MX records point to the inbox provider
MX records tell other mail servers where to deliver messages for a domain. An MX record names a mail server, often operated by an email provider, and has a priority value. If several MX records exist, senders generally try the lowest-numbered priority first and may try others when delivery fails. The named mail servers must also resolve to usable network addresses through their own DNS records.
Set MX records according to the provider that actually hosts the inboxes. Pointing MX at a web server does not make that server accept email; it must be configured to do so. Although some mail systems may try a domain’s address record when no MX record exists, that behavior is not a dependable substitute for an intentional receiving-mail setup.
A change of inbox provider is therefore primarily a receiving-mail change. Check that the new provider has created the mailboxes or routing rules before replacing the old MX records. DNS updates may take time to reach every sender because previous answers can remain cached.
Sending mail: SPF and DKIM identify legitimate senders
MX records do not grant permission to send mail. For outgoing messages, SPF and DKIM are two important DNS-based checks. An SPF record is published as a TXT record and lists systems permitted to send mail for a domain used in the message’s envelope sender address. A receiving server compares that record with the IP address of the system that connected to it. If you use more than one sending service, the SPF policy needs to account for each one without becoming a collection of conflicting SPF records.
DKIM works differently. A sending service signs parts of a message with a private key; its matching public key is published in DNS under a selector name supplied by that service. A receiving server can use the public key to check the signature. The private key belongs with the sending service, not in a public DNS record. Your email provider should supply the exact DNS name and value needed for its DKIM setup.
The sending server’s own hostname and IP address can matter too. Mail servers commonly use an address record for the hostname they present, while reverse DNS, or PTR, associates the sending IP address with a hostname. The operator of the IP address usually controls that PTR record. These details do not replace SPF or DKIM, but a sending provider may require them for a well-configured service.
DMARC connects authentication to the visible From address
The address readers see in the From field is not necessarily the address SPF checks. DMARC helps connect them. It evaluates whether SPF or DKIM passes and whether at least one passing result aligns with the domain in the visible From address. A message can therefore pass an SPF check for a service’s domain yet fail DMARC for your domain if the relevant domains do not align.
A DMARC policy is published as a TXT record at _dmarc.example.com for example.com. Policies can ask receivers to monitor, quarantine or reject messages that fail DMARC, though each receiver makes its own handling decisions. If you are setting up DMARC for the first time, verify that legitimate sending services authenticate with aligned domains before requesting stricter handling. Optional reports can help identify forgotten senders, but report destinations should be addresses you are prepared to manage.
Check each path separately when something breaks
If messages to your domain do not arrive, start with the MX records: do they name the intended inbox provider, and does that provider recognize the recipient? If your messages arrive in spam or are rejected, review the sending service’s SPF and DKIM instructions, DMARC alignment and any delivery error returned by the recipient’s server. An MX change is unlikely to fix authentication for outgoing mail.
Test using a domain you control and the DNS names supplied by your provider. Public DNS lookups can confirm that records are visible, while a test message and its authentication results can show how a receiver evaluated them. Keep account passwords, private keys and other credentials out of DNS records and troubleshooting screenshots. The useful question is not simply whether “email DNS” exists, but whether the records support the particular sending or receiving path you intend to use.



