Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To set up reverse DNS on a VPS, point a hostname’s A or AAAA record to the VPS address, then set that hostname as the address’s PTR record through the VPS provider. Verify that a reverse lookup of the IP returns the hostname and that the hostname resolves back to the same IP. For most rented VPSs, the provider controls the reverse DNS zone; adding a PTR record to your regular domain’s DNS zone will not change it.
What reverse DNS does—and who controls it
A PTR record maps an IP address back to a hostname. It is stored in the reverse DNS namespace for that IP, which is usually controlled by the organization that owns the address block. For a VPS customer, that generally means configuring PTR through the hosting provider’s console, API, or support team—not through the DNS panel where you manage your domain’s A, AAAA, and MX records. Cloudflare explains the distinction in its reverse-zone guide.
There are two practical routes: use the VPS provider’s rDNS feature, or manage a reverse zone yourself if you control the IP prefix and the relevant reverse-zone authority has been delegated to you. The second route is not typical for a tenant with an address assigned from a provider’s VPS network.
Set up reverse DNS on a VPS
- Identify the public IP address. Record the IPv4 address, IPv6 address, or both that the service will actually use. Do not configure a different address, such as a private interface address, by mistake.
- Choose one canonical hostname. For a mail server, this is commonly a name such as
mail.example.com. For another service, choose its stable public hostname. Use one PTR hostname per IP for a straightforward configuration. - Create the forward DNS record. In the DNS zone for your domain, create an A record for the hostname that points to the VPS’s IPv4 address, or an AAAA record that points to its IPv6 address. This forward record is separate from the PTR.
- Set the PTR with the IP owner. In the VPS panel, look for Networking, IP, or reverse DNS settings. Enter the chosen hostname and follow the provider’s validation rules. If no control is available, ask the provider whether it can set the PTR or delegate the reverse zone.
- Check both directions. Run
dig -x VPS_IP, replacingVPS_IPwith the actual address. The response should name your chosen hostname. Then look up that hostname and confirm its A or AAAA record includes the same IP. This matching is called forward-confirmed reverse DNS (FCrDNS).
Changes can take time to appear because of DNS caching. The provider documentation cited here does not establish one universal propagation period, so check again later or query another resolver rather than relying on a fixed wait time.
#1 Best Overall
Provider-specific settings
Hetzner Cloud
In Hetzner Console, select the cloud server, open Networking, and edit the rDNS entry next to the relevant IP. Hetzner’s Cloud Server rDNS instructions say a valid entry resolves in both directions. Make sure the hostname’s forward record points back to that server address. For IPv6, use the address assigned to the network interface and enter the interface identifier in the format the console expects.
Hetzner’s general PTR record documentation says its IP addresses have provider-managed PTR records that users can edit in Console or Robot; the PTR updates automatically when the value is changed. Hetzner also says one IP should not have multiple PTR hostnames. If the same IP serves mail and web traffic, it recommends using the mail-server hostname.
DigitalOcean Droplets
DigitalOcean creates a Droplet’s PTR automatically from its name when that name is a valid fully qualified domain name (FQDN). A generic name such as my-droplet is not a valid FQDN for this purpose. DigitalOcean says manual PTR creation is not available in its control panel, so use a suitable FQDN as the Droplet name and ensure its forward DNS points to the Droplet’s address. See DigitalOcean’s DNS record management documentation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsCloudflare and reverse zones you control
Cloudflare’s reverse-zone guide covers creating reverse zones and PTR records for IPv4 and IPv6 prefixes you control, then configuring the reverse-zone nameservers with the applicable Regional Internet Registry. Its examples include IPv4 reverse zones for /24 and /16 prefixes and nibble-reversed IPv6 names under ip6.arpa. This applies when you control the IP prefix and its reverse DNS authority; simply adding a PTR record to an ordinary domain zone does not establish reverse DNS for a provider-owned VPS address.
Choosing a PTR hostname for mail
For a mail server, use a stable mail hostname and make sure its A or AAAA record resolves to the same address whose PTR points back to it. If one IP handles both SMTP and web traffic, Hetzner recommends the mail-server hostname as the PTR target. The goal is a consistent forward-and-reverse relationship, not a list of every service hosted at the address.
A correct PTR is only one part of mail configuration. It does not prove domain ownership or guarantee that messages will be accepted. Cloudflare notes that SPF, DKIM, and DMARC provide better domain-ownership verification than PTR records. If delivery fails, check those records and the server’s SMTP behavior as well as rDNS.
Quick Recap
Rank #4
Troubleshoot reverse DNS problems
- The lookup still returns the provider’s default hostname: confirm that you changed the PTR for the correct public IP and saved the provider setting. Check whether the provider accepts the hostname format you entered.
- The provider rejects the hostname: use a fully qualified hostname and verify its A or AAAA record points to the assigned address. Some providers require forward DNS to be in place before accepting a PTR.
dig -xreturns no answer or an old value: recheck the IP and the provider’s rDNS status. Allow for caching and try another resolver; no universal propagation time is established by the cited provider documentation.- A PTR appears in Cloudflare, but the reverse lookup does not: check that you control the IP prefix and that the reverse zone is delegated to the nameservers serving it. A PTR in your regular domain zone is not a substitute for a record in the IP’s reverse zone.
- Mail still fails after the PTR is correct: verify the forward hostname, SPF, DKIM, DMARC, and SMTP behavior, then review the recipient’s delivery diagnostics. A matching PTR alone cannot guarantee delivery.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
