DigitalOcean creates a Droplet’s reverse DNS from its name, so the PTR is set by naming the Droplet with its full host name. But it blocks ports 25, 465 and 587 on every Droplet, so it cannot send mail directly anyway.
| Provider | DigitalOcean — Cloud provider |
| Where | The Droplet’s name |
| Before you set it | Name the Droplet with the host name |
| IPv6 | For the first IPv6 address only |
| Outbound port 25 | Blocked — use a relay |
Is reverse DNS right for your DigitalOcean server?
Enter the IP address the server sends mail from, or its host name: we look up its PTR record, check that the name leads back to the address, and say whether it is still the default.
Setting reverse DNS at DigitalOcean
- Name the Droplet with the full host name — mail.example.com: DigitalOcean creates the PTR from the name. Rename it in the control panel, or with doctl.
With doctl:
doctl compute droplet-action rename 123456789 --droplet-name mail.example.com
Before you set it
- A Droplet name that is a full host name — “ubuntu-s-4vcpu-8gb-fra1-01” does not work.
- An A record for that name pointing back, for forward confirmation — DigitalOcean does not check it.
Sending mail on port 25
DigitalOcean blocks ports 25, 465 and 587 on every Droplet, with no documented way to unblock them: it recommends an email sending service.
Worth knowing
Reserved IPs cannot have reverse DNS: mail must leave from the Droplet’s own address.
Addresses have no default PTR.
What changed
- 22 June 2022 — Port 25 blocked for all new accounts.
- 6 March 2025 — Ports 465 and 587 blocked on Droplets as well.
Sources
Checked on 27 September 2026 against these official sources:
- How to Create, Edit, and Delete DNS Records — docs.digitalocean.com
- Reserved IP Limits — docs.digitalocean.com
- Why is SMTP blocked? — docs.digitalocean.com
- DigitalOcean release notes archive — docs.digitalocean.com