FEmail Deliverability Glossary

Forward DNS (DNS Lookup)

A standard DNS lookup that resolves a hostname to an IP address — a basic sanity check that receiving servers perform on every inbound SMTP connection.

Forward DNS is a standard DNS lookup that resolves a hostname to an IP address. In the context of email deliverability, forward DNS is used to verify that your sending hostname can be resolved — a basic sanity check that is part of receiving server authentication.

See also PTR Record (Reverse DNS). Forward DNS and Reverse DNS together form the Forward-Confirmed Reverse DNS (FCrDNS) check that many receiving servers require before accepting messages.

Frequently Asked Questions

What is the difference between forward DNS and reverse DNS for email?

Forward DNS resolves a hostname to an IP address (e.g., mail.yourdomain.com → 198.51.100.15). Reverse DNS (PTR) maps an IP back to a hostname (198.51.100.15 → mail.yourdomain.com). For email deliverability, receiving servers use both: they check the PTR record of your sending IP to find a hostname, then verify with a forward DNS lookup that the hostname resolves back to the original IP. This is called Forward-confirmed Reverse DNS (FCrDNS). Failure at either step causes many receiving servers to reject or heavily penalize your messages.

Who controls reverse DNS records?

Reverse DNS records (PTR records) are controlled by the owner of the IP address, not the owner of the domain. This means if you're using a cloud provider (AWS, GCP, Azure), a dedicated server host, or an ESP, they control your IP's PTR records. You must contact your IP provider to set or change your PTR record — it cannot be done through your domain registrar's DNS panel. This is one of the most commonly missed steps in new email infrastructure setup. Provide your provider with the exact hostname you want (e.g., mail.yourdomain.com) and verify it's set correctly before starting warm-up.

What happens if my PTR record doesn't match my sending hostname?

A PTR record mismatch — where the IP's reverse DNS points to a different hostname than the one in your email headers — is treated as a significant red flag by receiving servers. Many enterprise mail gateways use strict FCrDNS checks and will reject mismatched connections outright with a 550 error. At major ISPs like Gmail and Outlook, mismatches don't cause outright rejection but do contribute to negative scoring that makes inbox placement harder. During warm-up, a mismatched PTR record undermines every positive engagement signal your network generates.

Related Terms

Get Started Today

Stop Guessing. Start Landing in the Inbox.

Improve your email deliverability with real engagement signals and full visibility into where your emails actually land.

Free 10-day trial · No credit card · Cancel anytime