DNS PTR record: what it is and how it works

A PTR record (Pointer record) is a type of DNS record that maps an IP address to a domain name. It’s the reverse of a standard A record, which maps a domain name to an IP address. This makes PTR records the foundation of reverse DNS lookup.

PTR records serve three main purposes:

1. Verifying mail server identity for email deliverability
2. Enabling network troubleshooting by identifying which domain is associated with an IP
3. Supporting security logging by replacing cryptic IP addresses with readable domain names.

Below, we’ll cover what PTR records are, how reverse DNS lookup works, how to check and set up a PTR record, and what happens when one is missing.

What is a DNS PTR record?

PTR stands for “Pointer” record. It’s a type of DNS record that does the opposite of what you might be used to:

Normally, when you type a website name into your browser, DNS helps translate that into an IP address. It’s like looking up a friend’s name in your phone contacts to get their number. A PTR record flips this on its head—it starts with the IP address and gives you the domain name. It’s like entering a phone number into your contacts and finding out who it belongs to.

PTR records live in a special part of the DNS called the “reverse DNS” lookup zone. When someone wants to find out what domain name is associated with an IP address, they perform a reverse DNS lookup.

For example:

• Let’s say you’ve got the IP address 192.0.2.1
• To do a reverse DNS lookup, this gets flipped and turned into: 1.2.0.192.in-addr.arpa
• The DNS system then looks for a PTR record for this reversed address
• If it finds one, it returns the associated domain name

How reverse DNS lookup works

Reverse DNS lookup is the process of querying DNS to find the domain name associated with a known IP address. It’s the inverse of a standard DNS query: instead of asking “what IP address does this domain point to?” a reverse DNS lookup asks “what domain name is associated with this IP address?”

Reverse DNS lookups rely on PTR records to answer that question. When a mail server, security system, or network monitoring tool performs a reverse DNS lookup on an IP address, it checks whether a PTR record exists for that IP and whether the result matches the expected domain.

Forward DNS vs. reverse DNS: What’s the difference?

Think of forward DNS and reverse DNS as two sides of the same coin:

• Forward DNS: This is what you’re probably most familiar with. It takes a domain name (like www.example.com) and returns an IP address. It’s like looking up a business name to get their phone number.
• Reverse DNS: This is where PTR records come in. It takes an IP address and returns a domain name. It’s like having a phone number and wanting to know what business it belongs to.

You might think, “This is all very interesting, but why go through all this trouble?” Well, reverse DNS lookups serve several purposes:

• Email verification: Many email servers check PTR records to help verify the sender’s identity. No PTR record? Your email might end up in spam.
• Troubleshooting: Network admins use PTR records to identify which devices communicate on their networks.
• Improved user experience: Users can see readable domain names instead of seeing cryptic IP addresses in logs or connection information.
• Security: Some security systems use PTR records as part of their checks to identify potentially malicious traffic.

PTR record format and syntax

A PTR record is made up of two main parts:

1. The IP address (in reverse)
2. The domain name it points to

Here’s an example of a PTR record:

1.2.0.192.in-addr.arpa.    IN    PTR    www.example.com.

Here’s what each part means:

• 1.2.0.192.in-addr.arpa.: This is our reversed IP address.
• IN: This stands for “Internet”. It’s just DNS-speak for “this record is for the internet.”
• PTR: This is the record type.
• www.example.com.: This is the domain name associated with the IP address. Notice the dot at the end? That’s actually important in your DNS—not a typo.

The reversed IP address and the “.in-addr.arpa” suffix are part of a system for managing reverse DNS lookups.

• The IP is reversed to create a unique domain name for each IP address. 
• The “.in-addr.arpa” part is a special domain set aside for reverse DNS lookups.

When you see 1.2.0.192.in-addr.arpa, it’s really just a way of writing the IP address 192.0.2.1 in reverse DNS form.

However, if you’re dealing with IPv6 addresses (and increasingly, we all are), the PTR record looks a bit different:

1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.    IN    PTR    www.example.com.

Don’t panic, though—it’s just the IPv6 address written backwards, digit by digit, with “ip6.arpa” at the end instead of “in-addr.arpa”.

A few more things to note about PTR records:

• They’re usually created on the DNS servers of the organization that owns the IP address block (often your ISP or hosting provider).
• Unlike some DNS records, there should generally be only one PTR record per IP address.
• The domain in the PTR record should have a corresponding A (for IPv4) or AAAA (for IPv6) record pointing back to the IP address. This is called “Forward-Confirmed reverse DNS” (FCrDNS).

PTR records vs. other DNS record types

PTR records are just one element in the DNS ecosystem. To understand their role, you need to see how they stack up against their DNS cousins.

A Records

A records are the most common type of DNS record. They do the job of linking a domain name to an IPv4 address.

• What they do: Point a domain to an IP address
• Example: example.com IN A 192.0.2.1
• How they differ from PTR: A records go from domain to IP, while PTR goes from IP to domain.

AAAA Records

AAAA records are basically A records for IPv6.

• What they do: Point a domain to an IPv6 address
• Example: example.com IN AAAA 2001:db8::1
• How they differ from PTR: Like A records, they go from domain to IP (just a longer IP), while PTR does the reverse.

CNAME Records

CNAME records create aliases for other domain names.

• What they do: Point one domain name to another domain name
• Example: www IN CNAME example.com
• How they differ from PTR: CNAMEs link domains to domains, not IPs to domains like PTR records.

MX Records

MX records tell email where to go.

• What they do: Specify mail servers for a domain
• Example: example.com IN MX 10 mail.example.com
• How they differ from PTR: MX records direct email traffic, while PTR records are often used to verify email servers.

TXT Records

TXT records hold pretty much any text information.

• What they do: Store text information in DNS
• Example: example.com IN TXT “v=spf1 include:_spf.example.com ~all”
• How they differ from PTR: TXT records are super flexible, while PTR records have a specific job (reverse DNS).

Where does PTR fit in?

PTR records help with:

1. Email verification: Many email servers check PTR records to help prevent spam.
2. Network troubleshooting: Sysadmins use PTR records for identifying devices on networks.
3. Improved logging: PTR records make logs more readable by showing domain names instead of IP addresses.

While A and AAAA records help you find where a domain lives, PTR records help you find out who lives at a particular IP address. It’s like the difference between “Where does John live?” and “Who lives at 123 Main St?”

How to check a PTR record

Before setting up a PTR record or troubleshooting a delivery issue, you’ll want to verify whether a PTR record exists for your IP address and what it currently resolves to.

Using the command line:

On Linux or macOS, use the dig command with the -x flag for a reverse lookup:

dig -x 192.0.2.1

Or use nslookup on any system:

nslookup 192.0.2.1

If a PTR record exists, the results will show the associated domain name. If the command returns nothing or an NXDOMAIN error, no PTR record is currently configured for that IP address.

Using an online lookup tool:

Several web-based tools perform PTR lookups without requiring command-line access. Tools like MxToolbox Reverse Lookup, WhatsMyDNS, and nslookup.io let you enter an IP address and see the PTR record result instantly, along with geographic information about who owns the IP block.

A properly configured PTR record should resolve to the fully qualified domain name (FQDN) of your mail server. For example: mail.yourdomain.com. That domain should also have a corresponding A record pointing back to the same IP address. I

f your PTR record resolves to a generic hostname assigned by your ISP or hosting provider (like 192-0-2-1.isp.net), you’ll need to request a custom PTR record that uses your actual domain name.

How to set up a PTR record

Unlike other DNS records, you typically can’t set up PTR records directly in your domain’s DNS settings. PTR records are usually managed by the owner of the IP address block, and that’s typically your Internet Service Provider (ISP) or hosting provider.

1. Identify your IP address

You need to know the IP address you want to set up a PTR record for. If you’re not sure, you can usually find this in your hosting control panel or by contacting your hosting provider.

2. Contact your ISP or hosting provider

Reach out to your ISP or hosting provider and ask them to set up a PTR record for your IP address. When you contact them, you’ll need to provide:

1. The IP address you want to set up the PTR record for
2. The domain name you want it to point to

For example, you might say: “I’d like to set up a PTR record for the IP address 192.0.2.1 to point to mail.example.com.”

3. Verify the setup

Once your provider has set up the PTR record, check that it’s working correctly. You can do this using a command line tool or an online service.

Using the command line (if you’re feeling a bit techy):

1. Open your command prompt or terminal
2. Type nslookup <your-ip-address> and hit enter
3. You should see your domain name in the results

For example:

> nslookup 192.0.2.1

1.2.0.192.in-addr.arpa name = mail.example.com.

4. Set up forward DNS (A or AAAA record)

You should also set up a forward DNS record (an A record for IPv4 or AAAA for IPv6) that points your domain to the IP address.

This you can usually do in your domain’s DNS settings:

1. Log into your domain registrar or DNS provider
2. Find the DNS management section
3. Add an A record (or AAAA for IPv6) pointing your domain to your IP address

For example:

mail.example.com.    IN    A    192.0.2.1

PTR records and email deliverability

For mail server administrators, PTR records directly affect whether outbound email reaches the inbox or gets flagged as spam.

When a receiving mail server processes an incoming message, it typically performs a reverse DNS lookup on the sending server’s IP address. If no PTR record exists — or if the PTR record doesn’t match the sending domain — many receiving servers will either reject the message outright or apply a spam scoring penalty.

Google, Microsoft, and most major mailbox providers check for a valid PTR record as part of their sender evaluation. Missing or mismatched PTR records are a common and easily overlooked cause of email deliverability failures that don’t produce obvious bounce errors.

Your PTR record should resolve to your mail server’s hostname:

192.0.2.1  →  PTR  →  mail.yourdomain.com

And that hostname should have a forward A record pointing back to the same IP:

mail.yourdomain.com  →  A  →  192.0.2.1

This bidirectional match is called Forward-Confirmed reverse DNS (FCrDNS).

Ultimately, PTR records are necessary but insufficient. A valid PTR record helps establish basic sending legitimacy, but it's one part of a broader email authentication stack. SPF, DKIM, and DMARC all play separate and equally important roles. 

What happens when a PTR record is missing

If your sending IP has no PTR record configured, reverse DNS lookups return no result. For general internet use, a missing PTR record is a cosmetic issue. Network logs show IP addresses instead of domain names, which is inconvenient but not critical.

For email, a missing PTR record is a more serious problem.

Most major mail servers and spam filters treat a missing PTR record as a trust signal failure. Without a PTR record for your sending IP:

• Your email may be rejected outright by mail servers that require reverse DNS as a minimum check
• Messages may be routed to spam even if SPF, DKIM, and DMARC all pass
• Google Postmaster Tools may flag your IP as having inadequate sending infrastructure
• Microsoft’s Exchange Online Protection uses reverse DNS as part of its inbound filtering evaluation

Common PTR record mistakes to avoid

Here are a handful of common PTR record mistakes we see:

• Mismatched forward and reverse DNS: Make sure your PTR record and A/AAAA record match.
• Incorrect formatting: PTR records are picky about format. Make sure you’re using the correct syntax.
• Forgetting to update: If you change your IP address, don’t forget to update your PTR record.
• Using a subdomain without proper setup: If you’re using a subdomain in your PTR record (like mail.example.com), make sure that subdomain is properly set up in your forward DNS too.

Get your email sending right with Valimail

Unfortunately, managing PTR records is just one piece of the complex puzzle that is email authentication and deliverability. Getting your emails to land in the inbox instead of the spam folder is easier said than done. You have to worry about:

• Setting up and maintaining PTR records
• Configuring SPF, DKIM, and DMARC correctly
• Keeping up with ever-changing email authentication standards
• Monitoring your email reputation

This is where we can help. Valimail provides the following to streamline your email authentication:

• Automated DMARC Enforcement: Valimail automatically enforces DMARC for you, which includes managing SPF, DKIM, and yes, those important PTR records.
• Real-time monitoring: We keep an eye on your email authentication 24/7, so you don’t have to.
• Easy-to-use dashboard: No more digging through command lines or DNS records. Our user-friendly dashboard gives you a bird’s-eye view of your email authentication status.
• Expert support: Our team of email authentication experts is always ready to help.
• Ongoing compliance: Valimail keeps your authentication up to date. We’re always one step ahead, so you don’t have to be.

Want to see how Valimail can help you reach (and maintain) DMARC enforcement?

Frequently asked questions