Skip to main content
Reverse DNS (rDNS) maps an IP address back to a hostname. This is commonly required for mail servers and is good practice for any production server. You have three options for managing rDNS records for your bare-metal server’s IP addresses.

​
Option 1: From the Customer Portal

Your server’s product details page includes an rDNS button next to your Primary IP in the Server Information panel. Click it to configure the PTR record for your primary IP address directly.

​
Option 2: DNS Manager

The customer portal includes a DNS Manager in the left sidebar. If you manage your DNS zones through DigitalFyre’s DNS Manager, you can configure PTR records there alongside your other DNS records.

​
Option 3: rDNS Delegation

If you manage your own DNS infrastructure and want full control over your PTR records, you can request rDNS delegation. DigitalFyre will delegate the reverse DNS zone to your nameservers, allowing you to manage PTR records yourself. To request delegation, open a support ticket at console.digitalfyre.com with your nameserver details and the IP range you need delegated.

​
Option 4: Support Ticket

If you prefer, open a support ticket at console.digitalfyre.com and provide:
  • The IP address(es) you need rDNS configured for
  • The hostname each IP should resolve to
Before setting a PTR record, ensure the forward DNS is already configured. The hostname should have an A record (IPv4) or AAAA record (IPv6) pointing back to the same IP address. Forward and reverse DNS should match.

​
Verifying rDNS

After configuration, verify the PTR record: 
# Check PTR for an IPv4 address
dig -x YOUR_IP_ADDRESS

# Alternative
host YOUR_IP_ADDRESS
The response should show your configured hostname.