What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To set up reverse DNS for a VPS, point a hostname’s A record (IPv4) or AAAA record (IPv6) to the VPS address, then set that hostname as the address’s PTR record through the VPS provider. The PTR is controlled by whoever manages the IP address’s reverse-DNS zone—not normally by the domain’s regular DNS zone. Verify that a reverse lookup returns your hostname and that the hostname resolves back to the same IP.
What reverse DNS does—and who controls it
A PTR record maps an IP address to a hostname. It resides in the reverse-DNS namespace for that address, which is usually managed by the IP owner or hosting provider. That is why adding a PTR record to the ordinary DNS zone for your domain does not, by itself, configure reverse DNS for a provider-owned VPS address. Cloudflare’s reverse-zone guide explains how PTR records and reverse zones work.
As an Amazon Associate I earn from qualifying purchases.
For a rented VPS, the practical route is usually the provider’s network, IP, or rDNS settings—or a request to the provider if there is no self-service option. A separate route applies if you control the IP prefix and the reverse-zone authority has been delegated to you: then you can manage the reverse zone yourself.
Set up the hostname and PTR record
- Identify the address the service will use. Record the VPS’s public IPv4 address, IPv6 address, or both. If you use both, configure and verify each address separately.
- Choose one canonical hostname. For a mail server, this is commonly a name such as
mail.example.com. For another service, choose its stable hostname. Use one PTR hostname per IP for a straightforward setup; Hetzner says an IP should not have multiple PTR hostnames in the ordinary configuration and recommends the mail-server hostname when mail and web services share an address. Hetzner’s PTR guidance covers its supported setup. - Create the forward record in your domain’s DNS zone. Add an A record for the hostname pointing to the VPS IPv4 address, or an AAAA record pointing to its IPv6 address. This forward record and the PTR are separate records, often managed in different places.
- Set the PTR with the IP address owner. In the VPS console, look for reverse DNS, rDNS, IP, or networking settings. Enter the chosen hostname, following the provider’s validation rules. If no setting 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, and confirm the result is the intended hostname. Then query that hostname and confirm its A or AAAA response includes the same IP. A PTR that points to a hostname resolving back to the address is called forward-confirmed reverse DNS (FCrDNS). Hetzner describes a valid rDNS entry as one that resolves in both directions. Hetzner’s Cloud Server rDNS instructions explain its check.
DNS caches can make a recent change appear inconsistent for a while. The provider documentation cited here does not establish one universal propagation time, so check again later rather than relying on a fixed deadline.
#1 Best Overall
Provider-specific setup paths
Hetzner Cloud
In Hetzner Console, select the cloud server, open Networking, and edit the rDNS entry next to the relevant IP. Hetzner says the hostname should resolve back to the IP. For IPv6, use the address assigned to the network interface and enter the interface identifier in the form the console expects. Hetzner’s general PTR guidance says its IPs have provider-managed PTR records that users can edit in Console or Robot; the PTR is updated when the value is edited. Cloud Server rDNS and PTR record document these details.
DigitalOcean
DigitalOcean documents automatic PTR creation for Droplets based on the Droplet name. The name must be a valid fully qualified domain name (FQDN); a generic label such as my-droplet is not sufficient. DigitalOcean says manual PTR creation through its control panel is unavailable, so use a suitable FQDN as the Droplet name and ensure its forward DNS points to the Droplet address. Its DNS-record instructions are at How to Create, Edit, and Delete DNS Records.
When you control the IP prefix
If you control the relevant IPv4 or IPv6 prefix and have reverse-zone authority, you can manage PTR records in that reverse zone. Cloudflare’s guide describes creating a reverse zone, adding PTR records, and configuring reverse-zone nameservers at the applicable Regional Internet Registry. Its examples include IPv4 /24 and /16 reverse-zone names and nibble-reversed IPv6 names under ip6.arpa. Most VPS tenants do not control the provider’s address prefix, so this approach requires the appropriate authority or delegation; creating a PTR in an ordinary domain zone is not enough. Cloudflare’s reverse-zone guide provides the details.
Reverse DNS for mail servers
For a mail server, use a canonical mail hostname as the PTR target and make its forward A or AAAA record resolve to the same IP. This matching is the FCrDNS check. If mail and web services share an IP, Hetzner recommends using the mail-server hostname for that address’s PTR.
A correct PTR is one part of mail configuration, not a guarantee that messages will be accepted or delivered. It does not by itself authenticate domain ownership. Cloudflare points to SPF, DKIM, and DMARC as better mechanisms for domain-ownership verification; configure and troubleshoot those separately from reverse DNS. Cloudflare’s guide discusses the distinction.
Quick Recap
Rank #4
Fix common reverse-DNS problems
- The lookup still shows the provider’s default hostname: confirm that you edited the correct public IP and saved the setting. Check whether the provider requires a particular hostname format.
- The provider rejects the hostname: verify that it is a fully qualified hostname and that its A or AAAA record points to the assigned VPS address, if the provider requires that before accepting a PTR.
- The reverse lookup has no answer or shows the old value: check the address and the provider’s rDNS status, then retry later or query another resolver to account for caching.
- A DNS dashboard shows a PTR, but
dig -xdoes not: check whether you control the IP prefix and whether its reverse zone is delegated to that DNS service. A PTR in your ordinary domain zone cannot replace the PTR for a provider-owned IP. Cloudflare’s reverse-zone guide explains the authority requirement. - Mail still fails after the PTR is correct: check the forward hostname, SPF, DKIM, DMARC, SMTP behavior, and the recipient’s diagnostic messages independently. A matching PTR does not resolve those other issues.
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.
