Getting Email Delivered - the ISIPP SuretyMail Blog

The Importance of Reverse DNS (rDNS) for Good Email Deliverability

This information is provided by SuretyMail Email Reputation Certification, getting email to the inbox for businesses of all sizes since 2003, guaranteed! For more information contact us here, or get started today here.

Just mention the term ‘DNS’, and many email senders’ eyes glaze over; say “rDNS” and a look of panic may replace the glaze. Yet, not only are these not complicated concepts, but having rDNS set up is critical to having consistent, good email delivery.

DNS, which stands for Domain Name System, translates domain names to the actual number-based address (known as an ‘IP address’) on the Internet at which the computer for that domain resides, allowing computers to find each other, such as to visit a website. Or, to send email to someone whose email is hosted at that computer.

Got questions about email deliverability or reputation? Contact us here!

Remember Lily Tomlin’s switchboard operator, Ernestine? Or, the Hooterville switchboard in Green Acres? (Am I dating myself here?) When Oliver Douglas wanted to talk with Sam Drucker, he picked up the phone, and told the operator “Connect me to Sam Drucker”, and the operator translated that to “connect Oliver to Sam’s telephone number.”

You can think of DNS as like those operators – you tell your computer “send email to” and the DNS system translates that to’s IP address.

So, for example, when you send email to me at my address at, your computer actually checks the DNS for – and it finds out that the server which you think of as “” is really known on the Internet as “that computer at IP address”

That IP address is what your computer needs to actually connect to our computer, and to transmit the email – to actually transfer the email from your computer to ours.

rDNS, or “reverse DNS”, allows the process to go the other way – when your computer connects to my computer to deliver an email message, it allows my computer to look at your computer’s IP address, and see what domain name your IP address claims to be.

Where DNS is like that switchboard operator, rDNS is like caller i.d.. Just as when you call me, my caller i.d. system takes your telephone number, and translates it to your name to be displayed on my caller i.d. box, so the rDNS system takes your computer’s IP address, and translates it to your computer’s domain name.

Here, roughly, is how that email transmission transaction works, in plain English. Let’s say you are trying to send email to me, and you are sending it from “”.

Your computer – the one which sends your email from “” – connects to my computer, and says “hello, I’m the computer at, and I have email for Anne at Anne’s email address.”

My computer says “Ok, I have that email address for Anne here, so I can accept and deliver email to her from you.”

“But FIRST,” my computer goes on to say (particularly in this day and age of spamming, spoofing, and phishing), “..first…let me check to make sure that you are really who you claim to be.”

Then my computer takes note of the IP address from which your computer – the computer claiming to be “” – is connecting to my computer. Let’s say that IP address is

My computer now has two pieces of information about you and your computer – your IP address, and that you are claiming to be “”.

If you are legitimate, then when my computer does a reverse DNS (rDNS) lookup, and asks the DNS system “what is the domain of the computer located at”, the answer needs to be “that computer is more commonly known as “”.

Then my computer knows that you are really who you say you are.

And delivers your email to me.

But if the DNS system says “that computer is more commonly known as”, well, my computer is going to refuse to accept email from you.

That probably makes sense to you. Perhaps you even knew that.

But what you may not have known is that if the DNS system says “that computer is more commonly known as..known as…well…we have no idea what it’s more commonly known as because they don’t have rDNS set up”, well, then a lot of computer systems, and ISPs (including some big ISPs) will refuse to deliver your email because they don’t know if they can trust you.

At the very least, even if they don’t outright refuse your email, they will immediately and seriously degrade the trust they give it, and just one more problem (such as a high level of complaints for email coming from your IP address due to poor opt-in quality, or poor scheduling, or having repurposed transactional email addresses) can tip the scales so that your email gets rejected.

And many, if not most, major ISPs now require working rDNS before they will even think about whitelisting you.

To determine whether your IP addresses have rDNS set up, you can use our handy tool to test whether you have rDNS set up.

If you don’t have rDNS set up, it’s not hard to get rDNS set up for your IP addresses. Usually it just takes a phone call or email to the support department of your ISP. If you are using an ESP (email service provider) to send out your email, you’ll want to talk to them.

This information is provided by ISIPP SuretyMail Email Reputation Certification, the only email reputation certification and deliverability assistance service with a money-back guarantee! For more information contact us here, or get started here.

Follow Us!

    Next: » How the Email Deliverability Accreditation and Reputation Industry is Eating Itself Alive

« Previously: Segregating Outbound Email Across Different IP Addresses Based on Opt-In Quality


Leave a Reply

This article originally written on May 11, 2016, and is as relevant now as when it was first written.