Overview
Reverse DNS maps IP addresses back to hostnames using PTR records. This is distinct from forward DNS (hostname to IP) — PTR records live in special reverse zones (in-addr.arpa.
for IPv4 and ip6.arpa. for IPv6). Reverse DNS is required by mail servers for spam
reputation checks and improves audit log readability.
Prerequisites
- An active Xloud account with appropriate permissions
- Access to the Xloud Dashboard (
https://connect.<your-domain>) or CLI configured with credentials - API credentials sourced (
source admin-openrc.sh)
The reverse zone for your IP range (e.g.,
1.168.192.in-addr.arpa.) is managed
automatically by the DNS service for addresses within your allocation. You do not need
to create or manage these reverse zones manually.How Reverse DNS Works
Configure a PTR Record
- Dashboard
- CLI
Navigate to Reverse DNS
Navigate to Project → DNS → Reverse DNS. Select the Floating IPs or
Fixed IPs tab depending on the IP type you want to configure.
Set the PTR record
Click Set next to the IP address and enter the fully qualified domain name
including the trailing dot (e.g.,
mail.example.com.).The PTR zone (e.g., 1.168.192.in-addr.arpa.) is managed automatically by
the DNS service — you do not need to create it manually.IPv6 PTR records use the
ip6.arpa. reverse zone. The DNS service handles
zone delegation automatically for addresses in your allocation.Manage PTR Records
IPv6 Reverse DNS
IPv6 PTR records follow the same process as IPv4, but the reverse zone uses theip6.arpa. domain. The DNS service handles the zone delegation automatically.
Set PTR record for an IPv6 floating IP
Next Steps
Manage Records
Add forward DNS records to complement your PTR configuration
Record Types Reference
Reference for all supported DNS record types
Troubleshooting
Resolve PTR record failures and zone delegation issues
DNS Admin Guide
Administer reverse zone pools and nameserver delegation