How to set reverse DNS (rDNS/PTR) records for your Cloud Server
Reverse DNS (rDNS) maps your cloud server's IP address back to a hostname. This is the opposite of a standard DNS record. Setting it correctly improves outbound email deliverability and helps other servers identify and trust your VPS.
This article shows you how to set a reverse DNS record for your one.com unmanaged Cloud Server, and how to fix the most common validation errors.
This requires an active IPv4 and/or IPv6 address assigned to your VPS, which is included with all our Cloud Server plans.
-
Why set a reverse DNS record?
- Email deliverability - If you're self-hosting outbound mail on your Cloud Server, many mail servers reject or flag messages from IP addresses without a matching forward-confirmed reverse DNS (FCrDNS) record.
- Server identification - Some services and monitoring tools use reverse DNS as a basic trust signal.
- Compliance - Some corporate mail gateways require FCrDNS as a baseline anti-spoofing check.
You'll typically need to set an reverse DNS record if you're running a mail server (such as Postfix or Exim) on your VPS, running services that verify the hostname of incoming connections, or troubleshooting why your outbound mail is landing in spam. It's optional for most other use cases.
Before you start
Your rDNS hostname needs an A or AAAA record pointing back to your Cloud Server's IP address, to confirm you control it. If that record doesn't exist yet, create it first, then come back to set the reverse DNS record.
-
How to set a reverse DNS record
- Go to your VPS page in the one.com Control Panel.
- Click on the name of the Cloud Server to open overview page of the oneHome Cloud Server.
- Go to Network in the left-hand menu.
- Click Reverse DNS next to the IP address you want to set.
- Enter the reverse DNS hostname and click Save.
Changing your reverse DNS record doesn't affect connectivity, it only changes how other systems identify your VPS through reverse lookups. If you see a validation error instead, check the Troubleshooting section below.
-
Troubleshooting
If you see a validation error or the record isn't behaving as expected, here are a few things to check.
-
The hostname doesn't point back to the server's IP address
Your hostname needs its own A or AAAA record that resolves back to your Cloud Server's IP address. Create that DNS record first, wait for it to become active, then set the reverse DNS record again.
-
My rDNS change isn't showing up yet
DNS propagation for reverse DNS records can take anywhere from a minute up to 48 hours. Try again later.
-
My hostname was rejected
Use only lowercase letters, numbers, and hyphens. Underscores aren't allowed in hostnames.
-
My domain uses Cloudflare and my DNS record is set, but I still get a validation error
This usually happens when Cloudflare's proxy is active. The proxy serves Cloudflare's IP addresses instead of your Cloud Server's real IP, so the forward-confirmation check (FCrDNS) fails. Set the record to DNS only in Cloudflare while the rDNS validation completes. You can re-enable the proxy afterwards.
-
I set a reverse DNS record but my mail still lands in spam
Reverse DNS is one deliverability signal among several. Also check that SPF, DKIM, and DMARC are correctly set up for your domain.
Related articles: -
The hostname doesn't point back to the server's IP address