<\/span>Domain Name Setup<\/span><\/h3>\nYou need a registered domain name. This is the domain from which you will be sending emails. Make sure you have full ownership and control of this domain, including access to its DNS management.<\/p>\n
<\/span>Dedicated SMTP Server Setup Requirements<\/span><\/h3>\nIf you are running your own mail server, make sure it is fully installed and running. Your SMTP software (such as Postfix, Exim, or another mail server application) should be configured and tested locally before you start pointing DNS records at it.<\/p>\n
<\/span>Access to DNS Management Panel<\/span><\/h3>\nYou need to log in to wherever your domain’s DNS is managed. This is usually your domain registrar (like GoDaddy, Namecheap, or Cloudflare). You should have the ability to add, edit, and delete DNS records.<\/p>\n
<\/span>Static IP Address Requirement<\/span><\/h3>\nYour mail server must have a static IP address, one that does not change. If your IP changes, your DNS records will stop working, and your emails will fail. This is especially important for the PTR record, which is tied to a specific IP.<\/p>\n
<\/span>Step-by-Step DNS Setup for Email Servers<\/span><\/h2>\nNow let us go through each step of the actual configure DNS records for mail server process.<\/p>\n
<\/span>Step 1 \u2013 Configure A Record for Mail Server<\/span><\/h3>\nGo to your DNS management panel and add a new A record.<\/p>\n
\n- Name\/Host<\/strong>: mail (this creates mail.yourdomain.com)<\/li>\n
- Type<\/strong>: A<\/li>\n
- Value<\/strong>: Your server’s static IP address<\/li>\n
- TTL<\/strong>: 3600 (or default)<\/li>\n<\/ul>\n
This record tells the internet where your mail server lives. All other email DNS records depend on this foundation being correct.<\/p>\n
<\/span>Step 2 \u2013 Configure MX Record for Incoming Emails<\/span><\/h3>\nAdd an MX record so other servers know where to send emails addressed to your domain.<\/p>\n
Name\/Host<\/strong>: @ (represents your root domain)
\nType<\/strong>: MX
\nValue<\/strong>: mail.yourdomain.com
\nPriority<\/strong>: 10
\nTTL<\/strong>: 3600<\/p>\nIf you have a backup mail server, add a second MX record with a higher priority number, such as 20. The lower priority number always wins.<\/p>\n
<\/span>Step 3 \u2013 Configure SPF Record for SMTP Authentication<\/span><\/h3>\nAdd a TXT record for SPF to authorize your mail server to send emails from your domain.<\/p>\n
Name\/Host<\/strong>: @
\nType<\/strong>: TXT
\nValue<\/strong>: v=spf1 ip4:YOUR.SERVER.IP.HERE ~all
\nTTL<\/strong>: 3600<\/p>\nReplace YOUR.SERVER.IP.HERE<\/strong> with your actual server IP. The ~all<\/strong> at the end means emails from unauthorized sources will be treated as a soft fail (marked suspicious but not rejected). If you want stricter control, use -all<\/strong> to hard fail and reject unauthorized senders.<\/p>\nImportant<\/strong>: Only create one SPF record per domain. Multiple SPF records break authentication.<\/p>\n<\/span>Step 4 \u2013 Configure DKIM Record for Email Security<\/span><\/h3>\nDKIM setup happens in two parts. First, generate a DKIM key pair on your mail server. Most mail server software has a built-in DKIM key generator. Once generated, you will have a public key to publish in DNS.<\/p>\n
Add a TXT record:<\/p>\n
Name\/Host<\/strong>: default._domainkey (or whatever selector you used during key generation)
\nType<\/strong>: TXT
\nValue<\/strong>: v=DKIM1; k=rsa; p=YOUR_PUBLIC_KEY_HERE
\nTTL<\/strong>: 3600<\/p>\nReplace YOUR_PUBLIC_KEY_HERE<\/strong> with the actual public key string from your server. This is usually a long string of characters. Copy it exactly – even a small error will break DKIM validation.<\/p>\nStep 5 – Configure DMARC Record to Prevent Spoofing<\/p>\n
Add a TXT record for DMARC:<\/p>\n
Name\/Host<\/strong>: dmarc
\nType<\/strong>: TXT
\nValue<\/strong>: v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com
\nTTL<\/strong>: 3600<\/p>\nHere is what each part means:<\/strong><\/p>\n\n- p = quarantine<\/strong>: – emails that fail authentication go to spam. Use p=none to start in monitor mode or p=reject for the strictest setting<\/li>\n
- rua = mailto<\/strong>: – the email address where aggregate reports will be sent Start with p=none monitoring, then move to p=quarantine, and finally p=reject once you confirm everything is working correctly.<\/li>\n<\/ul>\n
Step 6 – Configure PTR Record (Reverse DNS)<\/h3>\n
PTR records are not managed in your domain’s DNS panel. They are controlled by the owner of the IP address – usually your hosting provider or VPS provider.<\/p>\n
Contact your hosting company and request a reverse DNS (PTR) record for your server’s IP. Tell them you want it to point to mail.yourdomain.com<\/p>\n
For example:<\/p>\n
![\"DNS](\"http:\/\/www.idealsmtp.com\/blog\/wp-content\/uploads\/2026\/05\/DNS-setup-for-email-servers-300x160.jpg\")
<\/p>\n