> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Configure Reverse DNS (rDNS)

> Set up reverse DNS records for your FREAKHOSTING VPS IP to improve email deliverability, server identity verification, and anti-spam compliance.

## Setting Up Reverse DNS for Your VPS

Here is a quick way to think about Reverse DNS: normal DNS is like looking up a person's phone number in a contacts list — you know the name, and you find the number. **Reverse DNS (rDNS) works the other way around** — you have the phone number (your IP address), and you want to find out whose name is attached to it.

When another server on the internet sees traffic coming from your IP address, it can perform a reverse lookup to check whether your IP has a legitimate hostname associated with it. If it does, your server looks trustworthy. If it does not, alarm bells start ringing — especially for email servers.

This is why configuring rDNS is one of the most important things you can do after setting up a new VPS, particularly if you plan to send any email at all.

<CardGroup cols={2}>
  <Card title="Difficulty" icon="gauge-low">
    Beginner
  </Card>

  <Card title="Time" icon="clock">
    3 Minutes
  </Card>
</CardGroup>

***

## How Reverse DNS Affects Email Deliverability

This deserves its own section because it catches so many people off guard. Here is what happens behind the scenes every time your server sends an email:

1. Your server connects to the recipient's mail server and says "I have a message from `you@yourdomain.com`."
2. The recipient's mail server looks at your IP address and performs a **reverse DNS lookup** — it asks "what hostname is associated with this IP?"
3. If your IP resolves to something like `mail.yourdomain.com`, the mail server then does a **forward lookup** on `mail.yourdomain.com` to confirm it points back to your IP.
4. If both directions match (**Forward-Confirmed Reverse DNS**), your email passes this check. If they do not match, or if no rDNS record exists at all, your email is far more likely to land in the spam folder — or be rejected outright.

Major email providers like Gmail, Outlook, and Yahoo all perform this check. Without proper rDNS, you are essentially sending mail from an unverified source, and most providers will treat it accordingly.

***

## Configuring Reverse DNS

<Steps>
  <Step title="Navigate to Your Server">
    Log in at [cloud.freakhosting.com](https://cloud.freakhosting.com), click **Servers** in the top navigation bar, then click **Manage** next to the server you want to configure.
  </Step>

  <Step title="Open the Network Tab">
    Click on the **Network** tab in the server management navigation.
  </Step>

  <Step title="Click Reverse DNS">
    In the **IPv4 Addresses** table, find the IP address you want to configure. You will see a blue **Reverse DNS** button in the **RDNS** column — click it.
  </Step>

  <Step title="Enter the Hostname">
    In the dialog that appears, enter the **fully qualified domain name (FQDN)** you want to associate with this IP address. Choose a hostname that reflects your server's purpose:

    * `mail.yourdomain.com` — for a mail server (the most common use case)
    * `server.yourdomain.com` — for a general-purpose server
    * `vps.yourdomain.com` — a simple, descriptive option
  </Step>

  <Step title="Save the Record">
    Click **Save** or **Update** to apply the Reverse DNS record. The change typically takes effect within a few minutes on FREAKHOSTING's side, though full DNS propagation across the entire internet can take up to 24-48 hours.
  </Step>
</Steps>

<Important>
  For Reverse DNS to work correctly, the hostname you enter **must also have a forward DNS record (A record)** pointing to the same IP address. If you set your rDNS to `mail.yourdomain.com`, then `mail.yourdomain.com` must resolve to your server's IP address via an A record in your domain's DNS settings. Without this bidirectional match, rDNS verification checks will fail.
</Important>

***

## Why Reverse DNS Matters

<CardGroup cols={2}>
  <Card title="Email Deliverability" icon="envelope">
    The number one reason to configure rDNS. Email servers at Gmail, Outlook, Yahoo, and virtually every corporate mail system perform reverse lookups on incoming connections. Without a valid rDNS record, your emails are far more likely to be flagged as spam or rejected entirely — even if your SPF, DKIM, and DMARC records are perfect.
  </Card>

  <Card title="Server Identification" icon="id-card">
    When other systems perform a reverse lookup on your IP, a configured rDNS record shows a meaningful hostname like `server.yourdomain.com` instead of a generic ISP-assigned address like `31-59-58-152.static.provider.net`. This makes your server look professional and intentionally configured.
  </Card>

  <Card title="Security & Trust" icon="shield-check">
    Many security tools, intrusion detection systems, and monitoring services use rDNS as part of their verification process. A properly configured rDNS record signals that your server is legitimate and well-maintained — not a throwaway machine being used for spam or attacks.
  </Card>

  <Card title="Service Requirements" icon="clipboard-check">
    Some third-party services, payment gateways, and APIs require a valid rDNS record before allowing your server to connect. If you have ever been mysteriously blocked from an API and cannot figure out why, a missing rDNS record is a surprisingly common culprit.
  </Card>
</CardGroup>

***

## Best Practices for Reverse DNS

* **Match forward and reverse** — Ensure your rDNS hostname has a corresponding A record pointing back to your IP address. This bidirectional match is called **Forward-Confirmed Reverse DNS (FCrDNS)** and is the gold standard that email providers look for.
* **Use a real domain you own** — Set the rDNS to a hostname under a domain you control. Made-up or generic names will not pass verification checks and defeat the purpose of setting rDNS in the first place.
* **Use a descriptive hostname** — Choose something that reflects the server's role. `mail.yourdomain.com` for a mail server, `web.yourdomain.com` for a web server, or `vps1.yourdomain.com` if you have multiple servers.
* **One hostname per IP** — Each IP address can have exactly one rDNS record. If your server has multiple IPs, you can (and should) set rDNS on each one individually.
* **Verify after setting** — After saving your rDNS record, confirm it is working by running `dig -x YOUR_IP` from a terminal or using an online reverse DNS lookup tool. You should see your chosen hostname in the response.

***

## Practical Scenarios

<AccordionGroup>
  <Accordion title="I am setting up a mail server">
    This is the most critical scenario for rDNS. Set your rDNS to the hostname your mail server identifies itself as (the value in your SMTP HELO/EHLO). Typically this is `mail.yourdomain.com`. Then make sure `mail.yourdomain.com` has an A record pointing to your server's IP. Also configure SPF, DKIM, and DMARC records for your domain — rDNS is just one piece of the email authentication puzzle, but it is the piece that trips people up first.
  </Accordion>

  <Accordion title="I am running a web server only — do I still need rDNS?">
    Strictly speaking, web servers do not require rDNS to function. However, it is still good practice to configure it. Some security scanners flag servers without rDNS, and if your web application ever sends transactional emails (password resets, order confirmations), those emails will benefit from having rDNS properly set.
  </Accordion>

  <Accordion title="I set rDNS but my emails still go to spam">
    rDNS is necessary but not sufficient for good email deliverability. Make sure you also have: an **SPF record** listing your server's IP as an authorized sender, **DKIM signing** enabled on your mail server, a **DMARC policy** published in your DNS, and a clean IP reputation (check your IP against common blacklists at tools like MXToolbox).
  </Accordion>

  <Accordion title="How long does Reverse DNS take to propagate?">
    Changes typically take effect within a few minutes on FREAKHOSTING's infrastructure. However, remote servers may cache the old record for a while — full DNS propagation across the internet can take up to 24-48 hours. You can verify the record using `dig -x YOUR_IP` or online DNS lookup services.
  </Accordion>

  <Accordion title="Can I set Reverse DNS to any hostname?">
    You can enter any hostname, but for it to work properly, that hostname must have a forward A record pointing to your IP address. Without the matching forward record, rDNS verification checks (like those performed by email servers) will fail, making the rDNS record effectively useless.
  </Accordion>
</AccordionGroup>

***

<Note>
  ### Need Extra Help?

  If you encounter any issues, our support team is ready to assist:

  * **Live Chat:** Quick assistance via our website.
  * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
  * **Discord:** [Join our Community](https://discord.gg/freakhosting)
  * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)
</Note>

<Tip>
  ### Save on Your Hosting

  Ready to get a new server? Use code **KB20** at checkout for **20% off** your first month!
</Tip>

***

<div align="center">
  **Last Updated:** March 2026 | **VPS Support:** Reverse DNS simplified.
</div>