Scribd
Upload
2 views

how to configure reverse dns

Configuring Reverse DNS (rDNS) involves mapping an IP address back to a domain name using PTR records, primarily for email servers and network diagnostics. To set up rDNS, you must own the IP address or have it delegated, and the process includes checking IP control, accessing the reverse DNS zone, and setting a PTR record. Testing can be done using commands like 'dig -x' or online tools, and it's important to note that misconfigured rDNS can lead to emails being flagged as spam.

Uploaded by

modisanedipuo66
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
2 views

how to configure reverse dns

Configuring Reverse DNS (rDNS) involves mapping an IP address back to a domain name using PTR records, primarily for email servers and network diagnostics. To set up rDNS, you must own the IP address or have it delegated, and the process includes checking IP control, accessing the reverse DNS zone, and setting a PTR record. Testing can be done using commands like 'dig -x' or online tools, and it's important to note that misconfigured rDNS can lead to emails being flagged as spam.

Uploaded by

modisanedipuo66
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

how to configure reverse dns

ChatGPT said:
Setting up Reverse DNS (rDNS) means mapping an IP address back to a domain name—
essentially the opposite of regular DNS. This is mainly used for:

Email servers (to prevent mail from being flagged as spam)

Network diagnostics

Security logs

🔁 How Reverse DNS Works


Regular DNS: example.com → 123.45.67.89

Reverse DNS: 123.45.67.89 → mail.example.com

This is done using PTR records (Pointer Records) in the DNS system.

🔧 How to Configure Reverse DNS (PTR Record)


🧱 Prerequisites
You must own the IP address, or it must be delegated to you.

If you're on shared hosting or cloud (e.g., AWS, DigitalOcean), you usually set
rDNS via their dashboard or support.

✅ Step-by-Step (For a VPS or Server)


1. Check who controls the IP
Use this command:

bash
Copy
Edit
whois <your_ip>
Look for the "NetName" or "OrgName" field. That’s your provider (like AWS, Linode,
etc.).

2. Access the Reverse DNS Zone


Most often controlled by your VPS or hosting provider

If you're using your own IP space, you’ll manage it via your DNS provider (e.g.,
Cloudflare, BIND, PowerDNS)

3. Set a PTR Record


You need to point your IP to a valid hostname (which itself should resolve back to
that IP)

Example:

Your IP: 123.45.67.89

Your domain: mail.example.com

Set the PTR record:

Copy
Edit
89.67.45.123.in-addr.arpa. IN PTR mail.example.com.
Make sure mail.example.com has an A record pointing to 123.45.67.89 too (forward-
confirmed reverse DNS or FCrDNS).

🧰 rDNS Setup by Popular Providers

Provider How to Set PTR / rDNS


AWS EC2 Set via EC2 console or support ticket
Google Cloud Requires DNS record & PTR request
DigitalOcean Automatic for droplets; set via dashboard
Linode Via the Networking tab in Linode Manager
OVH / Hetzner Dashboard → IP management → Reverse DNS
✅ Test Your Reverse DNS
Use:

bash
Copy
Edit
dig -x <your_ip>
or:

bash
Copy
Edit
host <your_ip>
Online:

MXToolbox Reverse Lookup

⚠️ Important Notes
PTR records can only be set by the IP owner (e.g., hosting provider).

Misconfigured rDNS can result in emails being marked as spam or blocked by


Gmail/Outlook.

Changes can take up to 24–48 hours to propagate.

You might also like