About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Gmail's 550 5.7.25 means the message was blocked because of reverse DNS on the sending IP address. The SMTP errors page states it this way: "This message was blocked because the sending IP address doesn’t have a PTR record, or the forwarding DNS entry doesn’t reference the sending IP address. Gmail requires that sending IP addresses have a PTR record." The same entry continues: "Learn more about requirements for sending IP addresses. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines."
That is a block, not a delay. The same page has temporary texts for a missing or mismatched PTR, under 421 4.7.0 and 451 4.7.23. Those say mail has been temporarily rate limited. A 550 5.7.25 has already been blocked. Fix the DNS, then try a new message. Retrying the same message will not invent a PTR.
What the symptom means
A PTR record is the reverse lookup: the address maps to a hostname. The sender guidelines describe the pair Gmail wants.
"The public IP address of a sending SMTP server must have a corresponding PTR record that resolves to a hostname. This is called a reverse DNS lookup. The same hostname must also have an A (for IPv4) or AAAA (for IPv6) record that resolves to the same public IP address used by the sending server. This is called a forward DNS lookup."
The page repeats one requirement: "The sending IP address must match the IP address of the hostname specified in the Pointer (PTR) record."
The error text says "forwarding DNS entry". The guidelines call the same check a forward lookup, and they name the record type: A for IPv4, AAAA for IPv6. Both must agree. A PTR that names mail.example.com fails the test when mail.example.com has no A or AAAA, or when that address is a different IP from the one that connected.
This check is required for every sender, and again for senders of more than 5,000 messages a day. It is separate from SPF and DKIM. A message can pass SPF and still receive 5.7.25.
The guidelines also say to set up valid reverse DNS records of your sending server IP addresses that point to your domain, and to check the PTR with the Google Admin Toolbox Dig tool. The checks below use dig from the command line.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The public address has no PTR | 5.7.25, and dig -x returns no name |
Reverse lookup of the address that opened the SMTP connection |
| The PTR names a host whose A or AAAA is a different address | 5.7.25, and the forward lookup does not return the sending IP | Look up the hostname the PTR returned |
| IPv6 is used, and only an IPv4 PTR exists | 5.7.25 on IPv6 connections. The guidelines say an IPv6 authorisation error can mean the PTR is not using IPv6 | Repeat the reverse lookup on the IPv6 address |
| The PTR shown in a provider panel is not what a public lookup returns | Your provider's panel shows a PTR, and dig -x does not |
Trust the dig -x answer from a public resolver, not the panel |
| The server's address changed and the old PTR remains | 5.7.25 just after a move | Compare the IP in the bounce with the PTR you saved |
Prove the cause before changing anything
All of these are read-only. Use the public address of the server that connected to Gmail, not an address behind NAT that Gmail never sees.
1. Reverse-lookup the sending address. The dig manual's example for a reverse lookup is:
dig -x 192.0.2.1
Replace 192.0.2.1 with the sending address. -x sets the query type to PTR. An empty answer means the server that answered returned no PTR for that address. The manual's +short option gives a terse answer. The default, without +short, is the verbose form.
2. Forward-lookup the name you got. The manual's terse example is dig +short example.com, and the default type is A. For an IPv6 sender, query AAAA. The guidelines require the forward record to resolve to the same public address.
3. Confirm you asked the public DNS. A panel that shows a PTR you just typed is not the lookup Gmail made. Repeat dig -x from a network that is not your own resolver if the first answer looks stale.
Fix
The PTR is a reverse DNS record for the sending address. The change below is a request to whoever controls reverse DNS for that address. The domain's A or AAAA record is the forward record the PTR name must resolve to.
Save the records first. Run these commands. Each writes its own file, so a later save never overwrites an earlier one. An empty file means the record did not exist before:
dig +short -x <sending-address> > ptr-before.txt
dig +short A <chosen-host> > a-chosen-before.txt
If ptr-before.txt holds an old hostname, also save the record that hostname has:
dig +short A <old-ptr-hostname> > a-old-before.txt
Use AAAA instead of A for an IPv6 sender.
Risk: the next step changes the PTR, the name every receiver sees for that address, and adds or changes an A or AAAA record in your zone. A hostname with no matching A or AAAA fails the forward check. Changing the A record to chase a wrong PTR sends other services on that name to the mail server's address.
Ask whoever controls reverse DNS for the sending address to publish one PTR from the sending address to a hostname you own. In your own DNS, publish an A record (or AAAA, for an IPv6 sender) on that hostname, with the same public address. The guidelines say the two addresses must match.
To undo it: if ptr-before.txt holds a hostname, ask the PTR holder to put that hostname back. If it is empty, ask the PTR holder to remove the PTR you asked for. In your zone, if a-chosen-before.txt holds an address, put that address back on the chosen hostname. If it is empty, delete only the A or AAAA record you added.
Do not publish a PTR that points at a name you do not control. You cannot keep the forward record in step.
Example (illustrative): the server at 198.51.100.40 sends mail. dig -x 198.51.100.40 returns old-host.example.net, and the A record for that name is 198.51.100.8. Gmail returns 5.7.25. The administrator asks the address provider for a PTR to mail.example.com, and sets the A record for mail.example.com to 198.51.100.40.
Confirm the fix
dig -xon the sending address returns the hostname you chose.- The A or AAAA lookup for that hostname returns the same address.
- A new message from that server to a Gmail mailbox is accepted, or fails with a different code. 5.7.26 is authentication, not this PTR check.
What to watch afterwards
- After the server is renumbered, update the PTR and the forward record together.
- Each public address the server uses for SMTP needs its own pair. A second address with no PTR fails on its own.
- Shared addresses follow the reputation of every sender on them. The guidelines say the activity of any sender on a shared IP affects the others. A correct PTR does not repair a shared address that is listed for spam.
- IPv6 needs an IPv6 PTR. An IPv4 PTR does not cover an IPv6 connection.
Read next
Related articles you may want next.
- TroubleshootingGmail 550 5.7.26: the sender is unauthenticated. Publish SPF or DKIM that matches the mailGmail blocked the message with 550 5.7.26. Match the bounce text to SPF, DKIM or DMARC, then publish the record the sending server can pass.Read article
- HostingApplication Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTRApplication mail bouncing or junked after a migration? Read Authentication-Results, then fix SPF, DKIM, DMARC alignment, PTR and Microsoft 365 relay settings for the new path.Read article
- TroubleshootingOutbound mail times out after a move: the new host cannot reach port 25Mail queued and port 25 times out after moving to Azure, AWS or Google Cloud? Prove the block with a TCP test and switch to an authenticated relay.Read article
Risks and limits
- Reverse DNS for the address may not be yours to edit. Until whoever controls it publishes the PTR, Gmail still has nothing to look up.
- 5.7.25 does not test SPF, DKIM or DMARC. Mail can pass this check and fail 5.7.26.
Sources
- Gmail SMTP errors and codes — Google, no date shown, accessed 22 November 2026
- Email sender guidelines — Google, no date shown, accessed 22 November 2026
- BIND 9 manual pages: dig, version 9.20.22 — ISC, no date shown, accessed 22 November 2026
This article was originally published on .