1. Home
  2. Knowledge Base
  3. Product
  4. Compute
  5. How rDNS (Reverse DNS) works in CloudPe

How rDNS (Reverse DNS) works in CloudPe

Overview

This Knowledge Base explains how rDNS (Reverse DNS) works on CloudPe, how it is automatically created, and clarifies common doubts faced by customers and internal teams.

CloudPe 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 CloudPe

High-Level Flow

  1. Client creates a VM from the CloudPe CMP.
  2. Client provides or updates the hostname for the VM in the CMP.
  3. CloudPe backend rDNS automation runs every 1 hour.
  4. The automation reads VM IP and hostname details from the CMP.
  5. 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

  • CloudPe 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?

No.

CloudPe automatically handles rDNS creation.

Clients should NOT:

  • Raise requests for manual rDNS creation
  • Try to configure rDNS outside CloudPe
  • Expect instant rDNS creation

Clients SHOULD:

  • Ensure the correct hostname is set in the CloudPe CMP
  • Wait up to 1 hour for rDNS propagation

Common Questions & Clarifications

Q1: rDNS is not visible immediately after VM creation

Answer: This is expected. rDNS is created by an hourly backend automation. Please wait up to 1 hour.


Q2: Can support add rDNS manually?

Answer: No manual addition is required or recommended. The automated process will handle it.


Q3: What if the hostname is changed?

Answer: The updated hostname will be picked up by the next hourly automation run and rDNS will be updated automatically.

Was this article helpful?

Related Articles

This is a staging environment