Understanding Reverse DNS Policies at InterServer

Setting up Reverse DNS (rDNS) is one of those tasks that sounds complicated, but it’s actually pretty straightforward once you know the rules of the road. Whether you are running a mail server or just want your network configuration to look professional, getting your rDNS set up correctly is important.

Here is a quick guide on how we handle rDNS here at InterServer, how you can set it up, and the one Golden Rule you need to follow to keep it active.

---

Who Needs rDNS and How to Get It

First, let’s look at what service you are using with us, because that determines how you get this set up.

1. Dedicated Server Users

If you have a dedicated server, you have the most control. You can set up your reverse DNS record yourself right inside your portal.

• Log into my.interserver.net.
• Navigate to your server settings.
• Update the rDNS field directly.

(If you get stuck or prefer we handle it, you can always contact support, and we will do it for you.)

2. VPS Users

If you are on a Virtual Private Server (VPS), the process is slightly different. Currently, you cannot set this manually in the dashboard. Instead, simply open a support ticket requesting the change, and our team will apply it for you.

3. Webhosting, Storage, and Non-Root Packages

If you are using our standard Webhosting (Shared Hosting) or Storage packages where you don’t have root access, you do not need to worry about rDNS. It is not required for these services, and InterServer staff does not set custom rDNS records for these account types.

---

The “Golden Rule”: Forward Must Match Reverse

Before you request an rDNS record or try to set one up, there is a technical requirement you must meet. We don’t just set rDNS to “anything you want”—it has to be a valid loop.

The Rule: Your domain must already be pointing to the server IP address (Forward DNS) before we can point the IP address back to the domain (Reverse DNS).

A Practical Example

Let’s say your server IP address is 6.7.0.0 and you want to set your rDNS to server.domain.com.

1. Step 1 (You do this): Go to your domain registrar and create an “A Record” for server.domain.com that points to 6.7.0.0.
2. Step 2 (We do this): Now that the connection exists, we can set the Reverse DNS for 6.7.0.0 to point back to server.domain.com.

If server.domain.com does not resolve to your IP address, the system will not allow the rDNS to be created.

---

Important Policy: Keep It Valid or Lose It

To meet accepted internet standards, we run automatic verification checks. We need to ensure that the relationship between your domain and your IP remains valid over time.

If your domain stops pointing to our IP, the rDNS record will be automatically removed.

Common reasons this happens include:

• The domain expires.
• You move the domain to a different server.
• You change the hostname.

If our system checks your IP and sees that the domain no longer “claims” it (via Forward DNS), the Reverse DNS entry is deleted to maintain network hygiene. If you need it back later, just fix the Forward DNS and request the setup again.