Summer heat — everything melts, even our prices.−25%−25% on every annual plan, until Aug 31See plans
EQVPS

Set reverse DNS (PTR) for your dedicated IP

How to set a PTR record for your dedicated-IP VPS from the dashboard, why mail servers need it, and how to confirm it resolves both ways. Self-service, no support ticket.

Reverse DNS (a PTR record) maps your IP address back to a hostname — the opposite of a normal A record. Most services never look at it. Mail is the big exception: receiving servers routinely check that a sending IP has a PTR, and that it matches the hostname the server introduces itself as. Get it wrong and your mail gets filed as spam or refused outright, no matter how clean your SPF and DKIM are.

On EQVPS you set the PTR yourself from the dashboard — no support ticket, no waiting on us.

Set it from the dashboard

  1. Sign in and open Servers, then click the dedicated-IP server you want to set.
  2. Find the Reverse DNS panel on the server page. (It only appears on dedicated-IP plans — a NAT server has no IP of its own to point.)
  3. Enter the hostname you want the IP to resolve to — a fully-qualified domain you control, e.g. mail.yourdomain.com.
  4. Save. The record is applied immediately.

The panel shows the current PTR, so you can come back and change it whenever the hostname changes.

Make it forward-confirmed

A PTR on its own isn't enough for mail. Strict receivers want forward-confirmed reverse DNS: the PTR points the IP at a hostname, and that hostname's A record points back at the same IP. Both directions have to agree.

So if your IP is 203.0.113.10 and you set the PTR to mail.yourdomain.com, also create an A record in your domain's DNS:

mail.yourdomain.com.  A  203.0.113.10

Now the loop closes: IP → hostname → IP.

Check it worked

From any machine:

# reverse: IP should return your hostname
dig -x 203.0.113.10 +short
# forward: hostname should return the same IP
dig mail.yourdomain.com +short

Both should point at each other. If the reverse lookup still shows a default provider hostname (something like static.203-0-113-10.rev.example-isp.net), the change hasn't propagated to the resolver you're using yet — wait a little and check again.

Honest limits

If you're standing up a mail server from scratch, the mail server walkthrough covers SPF/DKIM/DMARC and the port-25 story alongside this. And if you're still deciding whether you even need a dedicated IP, here's the NAT-vs-dedicated breakdown.

FAQ

Do I need a dedicated IP to set a PTR?

Yes. A PTR record maps an IP back to a hostname, so you have to own the IP. NAT plans share an outbound address, so there's nothing to set rDNS on. This works only on dedicated-IP plans.

Why does my mail keep landing in spam even with SPF and DKIM?

SPF and DKIM authenticate the message; PTR authenticates the IP. Many receiving servers reject or downrank mail from an IP whose reverse DNS doesn't resolve, or doesn't match the sending hostname. Set the PTR to your mail hostname and make the forward A record point back to the same IP — that's forward-confirmed rDNS, and it's what they check.

How long does the PTR take to apply?

The change itself is applied right away when you save it. DNS caching elsewhere can take anywhere from a few minutes to a couple of hours to catch up, so if a check still shows the old value, give it a bit.

Can I send mail on port 25 right away?

Not by default. Outbound port 25 is closed on new servers to keep spam off the network. Setting the PTR is one requirement for running mail; getting outbound 25 opened is a separate step — reach out once your PTR, SPF, DKIM and DMARC are in order.

Comments

No comments yet. Be the first.

Leave a comment

Comments are moderated before they appear.