Free DNS guide and PDF

DNS for email: MX, reverse DNS, ports and MTA-STS, in order

For: anyone whose mail stopped arriving or started bouncing after a DNS change, a move to a new email host or a new sending server. Also for whoever inherited DNS that someone else set up years ago.

  • Eight checks in order, open on this page, no sign-up needed to read them.
  • The three sending ports at a glance, and what to check first for what you see.
  • The checks and both tables as a PDF you can print.

Send me the PDF

The cover of the PDF
PDF, 36 pages

The 60-second answer

Mail to your domain never arrives, a bounce says 5.7.25, or you changed a record and nothing happened. This guide walks the eight checks in order, from the record that brings mail in to the ones receivers look at before they trust what you send. Each step says how to check and which free tool helps. It is free and all of it is on this page.

  1. The MX record says where mail to your domain goes. It handles mail coming in, not going out. A missing, wrong or unreachable MX is the first thing to check when mail never arrives.

  2. Mail going out needs reverse DNS: a PTR record on your sending IP whose hostname points back to the same IP. Whoever owns the IP sets it, not your domain registrar.

  3. DNS changes are not instant. The TTL that was on the record before your change decides how long the old answer lives, and nothing flushes it. Lower it before you change anything.

Every explanation on this page comes from the Email Almanac, our own library of more than 4,000 answers about email. You do not have to buy anything to read it.

Free PDF, 36 pages

Take the eight checks with you.

The steps, the ports table and the decision table, as a PDF you can print.

We send the PDF to this address and nothing else unless you tick the box. Unsubscribe in one click, any time.
  1. You get one email.It comes from Review My Emails, with the PDF link inside.
  2. Your PDF is the whole guide.The eight checks, the ports table and the table of what to check first, ready to print.
  3. Nothing else, unless you ask.No newsletter unless you tick the box. Unsubscribe in one click, any time.

Which case are you?

Your domain's DNS, under review.

Two taps: where the trouble is, then what you see. The card shows the record to check first.

Answer here and your row lights up, with what to do first. The PDF has every row and the full guide.

I know my row
Read in your browser only. Nothing you type or pick is sent to us or stored.

Domain DNS under review

Example
Mail coming in
Mail going out
The records receivers check

The reasoning, in plain English

Check this first

    The guide

    The eight DNS checks, in order

    One line each. Tick them as you go. Open a step for the full explanation.

    0 of 8 done
    1. Part 1. Mail coming in: MX, and changing records safely

    2. 1

      Why:no answer section means no MX record, and no mail comes in.

      Read the full explanation

      The MX record tells sending servers which host accepts mail for your domain. Each one has a hostname and a priority number, and the lower number is tried first. To check, run dig MX yourdomain.example on Mac or Linux, or nslookup -type=MX yourdomain.example on Windows, and look for an answer section that lists your mail servers. No answer section means no MX record, and a hostname that does not match what your email host gave you, even by one character, means no mail comes in. Without one, mail to you bounces, and you hear about it from a forwarded bounce or a colleague, not from an alert. Add the record your email host gives you at your DNS provider. Mail that bounced while it was missing is gone, and senders have to send it again.

    3. 2

      Why:an MX left pointing at the old server sends mail there, to be rejected. And never point an MX at a CNAME.

      Read the full explanation

      An MX record points to a hostname. The sending server then looks up that hostname's A record to get an IP address, and connects to it on port 25. So check the record was updated after your last move. An MX left pointing at the old server sends mail there, to be rejected, dropped or bounced days later. And check the MX hostname has its own A record, the most likely cause of an "invalid MX record" error, and that the MX does not point to a CNAME, which DNS rules do not allow.

    4. 3

      Why:lower it to 300 at least 48 hours ahead. Nothing you do flushes the copies already held.

      Read the full explanation

      How long a change takes to show depends on the TTL. At 300 seconds most resolvers see it within 5 to 30 minutes, at 3600 within 1 to 4 hours, and at 86400 it can take 24 to 48 hours. The TTL that counts is the one on the record before you changed it, and nothing you do at your DNS host flushes the copies already held. So lower the TTL to 300 at least 48 hours ahead, make the change, then raise it again once it works. When you move mail to a new server, keep the old MX live next to the new one, with the new one at the lower number, until mail is arriving cleanly on the new server.

    5. Part 2. Mail going out: reverse DNS and ports

    6. 4

      Why:whoever owns the IP sets it, usually your hosting provider, not your domain registrar.

      Read the full explanation

      A PTR record maps an IP address back to a hostname. Whoever owns the IP sets it, usually your hosting provider, not your domain registrar. If you send through an email marketing tool on shared IPs, it has already set them. On a dedicated IP or your own mail server, you sort it out with your provider. Receivers check it when you connect, before SPF, DKIM or DMARC are even looked at. Pick a hostname that matches the name your server gives when it says hello (the HELO or EHLO name), such as mail.yourdomain.example. Publish an A record for that name first, then ask the IP owner to set the PTR to it.

    7. 5

      Why:the IP points to the hostname, and the hostname points back to the same IP.

      Read the full explanation

      Forward-confirmed reverse DNS (FCrDNS) means both directions agree: the IP points to the hostname, and the hostname points back to the same IP. To check, run dig -x with your sending IP and note the hostname, then run dig A on that hostname and confirm the same IP comes back. A bounce with 5.7.25 usually points to a reverse DNS problem. The usual causes are no PTR at all, a PTR whose hostname does not point back to the IP, or a generic hostname that looks like a home or dynamic connection.

    8. 6

      Why:port 587 is for you, or your app. If 587 does not work, try 465.

      Read the full explanation

      Port 25 is for mail servers talking to each other. Port 587 is for you, or your app, handing mail to your own mail server after logging in. Most ISPs block outbound port 25 from home and cloud IPs, so set your app or mail program to 587. Port 465 is the older secure port that encrypts the whole connection from the start. If 587 does not work, try 465. In a connection test, "timed out" is silence: the server may be down or overloaded, or a firewall is dropping the traffic. "Refused" is a clear no: the port is closed, the mail service is not running, or a rule blocks your IP.

    9. Part 3. The records receivers check: MTA-STS, TLS-RPT and the TXT records

    10. 7

      Why:the usual faults: the file at the wrong path, a broken certificate, the TXT record without its underscore.

      Run the free MTA-STS checker

      Read the full explanation

      MTA-STS tells sending servers that mail to you must travel encrypted. It has two parts: a TXT record at _mta-sts.yourdomain.example, and a policy file served over HTTPS at https://mta-sts.yourdomain.example/.well-known/mta-sts.txt that sets the mode and lists the mail servers allowed to receive for your domain. The usual faults are the file at the wrong path, an expired or broken certificate on that host, the TXT record without its underscore, and switching to enforce before testing. TLS-RPT is a TXT record at _smtp._tls.yourdomain.example that asks sending servers for a daily report when encrypted connections to you fail. Our free MTA-STS and TLS-RPT checker reads all of it.

    11. 8

      Why:two SPF records fail SPF for every message. Two DKIM records are fine under different selectors.

      Check your SPF recordCheck your DMARC recordThe SPF lookup limit guide

      Read the full explanation

      SPF, DKIM and DMARC each live in their own TXT record: SPF at the domain itself, DKIM at a selector name under _domainkey, and DMARC at _dmarc. Two SPF records on one domain fail SPF for every message, and two DMARC records usually mean receivers ignore your policy. Two DKIM records are fine under different selector names. SPF also has a limit of 10 DNS lookups. Run the free SPF and DMARC checkers, and for the lookup limit read our guide "SPF permerror and the 10 lookup limit".

    Your plan

    Answer the questions above, then tick the steps.

      Ask the free SOS line
      Capture not live yet. We send the plan and nothing else unless you ask.
      See every row of the table

      What you see, and what to check first

      What you seeCheck this first
      Mail to your domain bounces or never arrivesRun dig MX on your domain. No answer section means no MX record. Add the one your email host gives you
      "Invalid MX record" or "MX lookup failed"Give the MX hostname its own A record, and do not point the MX at a CNAME
      You changed DNS and nothing happened, or some mail works and some failsServers still hold the old record until the old TTL runs out, and nothing flushes it. Wait it out, and lower the TTL before the next change
      550 5.7.25, or "no reverse DNS"Reverse DNS. Check your sending IP has a PTR, that its hostname points back to the IP, and that the name is not generic. Ask whoever owns the IP to fix it
      The PTR is set, but some receivers still defer or reject you at connectionMake the hello name (HELO), the PTR and the A record all agree
      Your app or mail program cannot connect on port 25Use 587 with a login. Port 25 is often blocked outbound from home and cloud IPs. If 587 fails, try 465
      "Connection timed out" or "connection refused" when sending to a domainTimed out is silence, from a server that is down or a firewall that drops it. Refused is a clear no. Check that domain's MX records, and whether it is one domain or many
      The MTA-STS checker shows errorsCheck the policy file is exactly at /.well-known/mta-sts.txt, its certificate is valid, and the TXT record is at _mta-sts with the underscore. If mail bounces in enforce mode, switch back to testing while you fix it
      Mail to you bounces after a certificate expired, with MTA-STS on enforceRenew it. Senders keep your cached policy for its max_age, so mail can fail for a while after renewal. Next time renew at least two weeks ahead
      SPF permerror, or your DMARC policy seems ignoredLook for two SPF records or two DMARC records on the domain, and keep exactly one of each. Then run the free SPF and DMARC checkers
      The free MTA-STS and TLS-RPT checker

      Setting up MTA-STS or TLS-RPT? Run the free MTA-STS and TLS-RPT checker.

      Ports 25, 587 and 465 at a glance
      PortWhat it is forWhen you use it
      25Mail servers handing mail to each other, with no loginWhen you run a mail server that receives mail. Often blocked outbound from home and cloud IPs
      587Sending from your app or mail program after logging in, with STARTTLS encryptionThe default for sending
      465The older secure port, encrypted from the startWhen 587 does not work
      See how it plays out for a real business

      Worked example. Gil Brinewater runs Barnacle & Bloom, a florist. A customer says an order sent to gil@barnacle-bloom.example bounced. Ping set up the shop's DNS years ago, so Gil asks him. Ping runs dig MX barnacle-bloom.example and the answer still names the mail host the shop moved away from last month. An MX left pointing at an old server sends mail there to be rejected or dropped. Ping enters the values the new email host gives, exactly as given. The old record had a TTL of 86400, so some servers keep the old answer for up to a day, and nothing speeds that up now. Then the shop's invoices, sent from its own small server, bounce with 550 5.7.25, which usually points to reverse DNS. Ping adds an A record for mail.barnacle-bloom.example, then asks the hosting provider to set the PTR to that name. Last, the free MTA-STS checker shows the policy file still lists the old mail host. The policy lists which mail servers may receive for the domain, so Ping updates it to match.

      Who we are

      About Review My Emails

      Review My Emails is email list cleaning and validation that tells you which addresses to keep, which to watch and which to stop sending to, and why.

      Most checkers answer one question: does this address exist? We answer the next one: should you send to it? An address can be perfectly valid and still be quietly damaging your sender reputation. Valid is not safe.

      The company was founded in 2020 and is based in Bolton, United Kingdom. Our founder is Yanna-Torry Aspraki, an email deliverability specialist who has worked in deliverability since 2015.

      Your next step. Use the free tools as you go: the MTA-STS and TLS-RPT checker (reviewmyemails.com/tools/mta-sts-checker), the SPF checker (reviewmyemails.com/tools/spf-checker), the DMARC checker (reviewmyemails.com/tools/dmarc-checker), and the blocklist check (reviewmyemails.com/tools/blacklist-checker) if a bounce names a list. For MX, use the dig MX command from step 1. For SPF in depth, read "SPF permerror and the 10 lookup limit" (reviewmyemails.com/resources/spf-lookup-limit). For a bounce code you do not recognise, read "Bounce codes, decoded: what yours means and what to do next" (reviewmyemails.com/resources/bounce-codes-decoded). Stuck, or not sure which record is wrong? Ask the free SOS line at reviewmyemails.com/sos. A real person answers, with no pitch.

      List cleaning does not fix SPF, DMARC, MX or blocklist problems. Those live in your sending setup, and they are a different job. A blocklist listing measures your sending, so it is never a reason to suppress anyone on your list. And nobody can promise you the inbox, so we do not.

      Yanna-Torry Aspraki, Review My Emails

      Email SOS Hotline, free

      Stuck? We are here.

      For those problems there is the Email SOS Hotline, our free help line. Tell Yanna-Torry what is going on and she will tell you what she would do. She reads every message herself and replies within 48 to 72 hours, with no pitch.

      Ask the free SOS line
      The cover of the PDF

      Free PDF, 36 pages

      Want this as a PDF?

      Same eight checks, with the ports table.

      We send the PDF to this address and nothing else unless you tick the box. Unsubscribe in one click, any time.
      Words used
      MX record
      the DNS record that tells sending servers which host accepts mail for your domain, with a priority number
      TTL (Time To Live)
      the number of seconds other servers may keep a copy of your record before asking again
      Propagation
      the time it takes for a change to spread as the old copies held around the internet expire
      PTR record (reverse DNS)
      the record that maps an IP address back to a hostname, set by whoever owns the IP
      FCrDNS
      forward-confirmed reverse DNS. The PTR points to a hostname, and that hostname's A record points back to the same IP
      MTA-STS
      a policy your domain publishes saying mail to you must travel encrypted with a valid certificate
      TLS-RPT
      a TXT record that asks sending servers for daily reports when encrypted connections to you fail
      Where this came from: the Review My Emails Email Almanac.
      Review My EmailsTrust beats tactics™

      Founded in 2020, based in Bolton, United Kingdom.

      reviewmyemails.com/resources/dns-for-email?c=web-p10-r12pdf · v1

      Spotted something out of date?