Overview
This Knowledge Base explains how rDNS (Reverse DNS) works on Cloud, how it is automatically created, and clarifies common doubts faced by customers and internal teams.
Cloud follows a fully automated rDNS creation process. Customers do not need to manually add or manage rDNS entries after creating a Virtual Machine (VM).
What is rDNS?
Reverse DNS (rDNS) maps an IP address back to a hostname.
- Forward DNS: hostname → IP address
- Reverse DNS (rDNS): IP address → hostname
rDNS is commonly used for:
- Email server reputation and spam checks
- Network identification
- Compliance with hosting and email best practices
How rDNS Works in Cloud
- Client creates a VM from the Cloud CMP.
- Client provides or updates the hostname for the VM in the CMP.
- Cloud backend rDNS automation runs every 1 hour.
- The automation reads VM IP and hostname details from the CMP.
- rDNS entry is automatically created in DNS.
No manual action is required from the client or support team.
rDNS Creation Schedule
- rDNS is not created instantly.
- The backend automation runs on an hourly interval.
- rDNS entries are usually visible within 1 hour after VM creation or hostname update.
If rDNS is checked immediately after VM creation, it may not appear yet. This is expected behavior.
Backend Automation Details
Cloud runs an automated rDNS creation in the backend.
- Scans newly created or updated VMs
- Fetches IP address and hostname from the CMP
- Automatically adds or updates rDNS records in DNS
Key Points
- Automation runs hourly
- Fully automated
- Prevents manual errors
- Ensures consistency across the platform
Do Clients Need to Add rDNS Manually?
Cloud automatically handles rDNS creation.
Clients should NOT:
- Raise requests for manual rDNS creation
- Try to configure rDNS outside Cloud
- Expect instant rDNS creation
Clients SHOULD:
- Ensure the correct hostname is set in the Cloud CMP
- Wait up to 1 hour for rDNS propagation