In this article we are going to learn how to add a reverse DNS record (also known as a PTR record) to map your server's IP address to a domain name. The process is fairly simple so let's jump in and add our first reverse DNS record (RDNS).
Reverse DNS records are essential for those running a mail server since many recipient servers reject, or mark as spam, all email that originates from an “unauthenticated” server.
This basically means that after the sending IP address is checked, if the reverse DNS does not match the sending domain, then it is classed as “unauthenticated”.
We put ”unauthenticated” in quotes because having a Reverse DNS record attached to your domain does not automatically guarantee acceptance of email originating from your domain by the recipient's email server. It's just that non-matching or generic reverse DNS lookup settings are often rejected out of hand. Having a reverse DNS record for your domain will prevent email originating from your domain from getting immediately rejected.
RDNS can also be very useful when tracking down network issues and was the original driving force of RDNS. When pinging a website or IP address, one part of the output is the server's RDNS record.
When you enter a domain name into your browser, the DNS system will find the IP address of the server the domain is associated with.
A reverse DNS lookup does the opposite. It establishes what domain is associated with the IP address. This is a useful setting to configure for anyone but essential for customers running an outgoing mail server on their Cloud Server.
You can easily set up reverse DNS through the control panel. Just perform these steps:
Now that you know how to make changes to your DNS configuration, we're going to teach you a useful way to check your settings using the
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License