Setting Up Reverse DNS (PTR Records) for Your VPS

What Is Reverse DNS?

Reverse DNS (rDNS) maps an IP address back to a hostname. While forward DNS resolves mail.example.com → 198.48.63.241, reverse DNS resolves 198.48.63.241 → mail.example.com.

Why It Matters

• Email delivery — many mail servers reject messages from IPs without valid rDNS
• Security tools — logging and monitoring tools display hostnames via rDNS
• Verification — some services check that forward and reverse DNS match (FCrDNS)

Setting Up rDNS

Reverse DNS is controlled by the IP address owner (your hosting provider). For Kazepute Breezes, you can set the PTR record through your server dashboard or by contacting support.

Verifying rDNS

# Check PTR record
dig -x 198.48.63.241 +short

# Or using host command
host 198.48.63.241

# Check Forward-Confirmed rDNS
PTR=$(dig -x 198.48.63.241 +short)
echo "PTR: $PTR"
dig "$PTR" A +short

rDNS for Email Servers

For reliable email delivery, ensure:

1. Your server IP has a PTR record pointing to your mail hostname
2. The mail hostname resolves back to the same IP (FCrDNS)
3. The PTR hostname matches your SMTP HELO/EHLO hostname

Common Issues

• No PTR record — contact your hosting provider to set one
• Mismatched records — PTR and A record should point to each other
• Propagation delay — PTR changes can take up to 24 hours to propagate
• Multiple IPs — each IP needs its own PTR record