Skip to main content

​
Setting Up Reverse DNS for Your VPS

Reverse DNS (rDNS) maps your server’s IP address back to a hostname — the opposite of what standard DNS does. Configuring an rDNS record is essential for services like email, where receiving mail servers check that your IP address resolves to a legitimate hostname. A properly configured rDNS record improves email deliverability and adds credibility to your server’s identity.

Difficulty

Beginner

Time

3 Minutes

​
Configuring Reverse DNS

1

Navigate to Your Server

Click on Servers in the top navigation bar, then click Manage next to the server you want to configure.
2

Open the Network Tab

Click on the Network tab in the server management navigation.
3

Click Reverse DNS

In the IPv4 Addresses section, locate the IP address you want to configure and click the Reverse DNS button next to it.
4

Enter the Hostname

In the dialog that appears, enter the fully qualified domain name (FQDN) you want to associate with this IP address. For example:
  • mail.yourdomain.com
  • server.yourdomain.com
  • vps.yourdomain.com
5

Save the Record

Click Save or Update to apply the Reverse DNS record. The change typically propagates within a few minutes, though full DNS propagation can take up to 24-48 hours.

​
Why Reverse DNS Matters

Email Deliverability

Most email servers perform rDNS lookups to verify the sender. Without a valid rDNS record, your emails are much more likely to be marked as spam or rejected entirely.

Server Identification

When other systems perform a reverse lookup on your IP address, a configured rDNS record shows a meaningful hostname instead of a generic ISP-assigned address.

Security & Trust

Many security tools and services use rDNS as part of their verification process. A properly configured rDNS record signals that your server is legitimate and well-maintained.

Service Requirements

Some third-party services and APIs require a valid rDNS record before allowing your server to connect or send data.

​
Best Practices for Reverse DNS

  • Match forward and reverse — Ensure your rDNS hostname has a corresponding A record pointing back to your IP address. This bidirectional match is called a Forward-Confirmed Reverse DNS (FCrDNS) and is considered best practice.
  • Use a real domain you own — Set the rDNS to a hostname under a domain you control, not a made-up or generic name.
  • Use a descriptive hostname — Choose a hostname that reflects the server’s purpose (e.g., mail.yourdomain.com for a mail server).
  • One hostname per IP — Each IP address can have exactly one rDNS record.
Changes typically take effect within a few minutes, but full DNS propagation across the internet can take up to 24-48 hours. You can verify the record using tools like dig -x YOUR_IP or online DNS lookup services.
While rDNS is most critical for mail servers, it is still good practice to configure it for all servers. It provides a professional identity and may be required by certain services or security scans.
You can enter any hostname, but for it to work properly, that hostname should have an A record pointing to your IP address. Without the matching forward record, the rDNS record alone may not satisfy verification checks.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!
Last Updated: March 2026 | VPS Support: Reverse DNS simplified.