If you are seeing a DNS:NR error when you attempt to connect to AOL's mx record, we are refusing your connection because the server you are using to send email has no reverse-DNS, or pointer record associated with the IP.
We have been refusing emails from servers with no reverse DNS for years, so this is nothing new. However, the mechanism we were using until recently still allowed a trickle from those servers through.
We recently fixed the glitch, so you may find your emails are now entirely refused, rather than trickling through at a very slow rate.
For those senders who have opened tickets with our Postmaster team and have updated their pointer records accordingly (and who now have reverse-DNS), based on how our lists are aggregated/pushed into production, you may see a 24 - 36 hour delay between when your DNS configurations are updated, and when you are successfully sending emails again to our system.
- Margot.
Do you have a DNS:NR error?
Recent Posts
- Receiving Issue Today (5/16/2013)
- New Spam Filtering (5/06/2013)
Reader Comments (Page 2 of 2)
21. This has been an on going issue for a server of ours for over 2 weeks now- You keep saying its fixed -when its not.. We needs this resolved!
Posted at 8:31AM on Apr 1st 2011 by Craig Hanselman
22. This is a huge problem and its been going on for over 3 weeks with no resolution. We have multiple servers that have DNS blocks when in fact our rev DNS is valid and working. AOL PLEASE fix this!
Posted at 10:43AM on Mar 30th 2011 by Craig Hanselman
23. Hi all... it would be helpful, if you are still receiving DNS:NR errors and it has been a full 36 hours following propagation of your new PTR record, if you would include your ticket number in your comment so we can research. For those who are receiving other errors, please continue to work with the Postmaster who reaches out to you. Thanks!
Posted at 10:37AM on Mar 31st 2011 by Margot Romary
24. I have 2 Support Tix: 987 and 2413- Thanks
Posted at 10:50AM on Mar 31st 2011 by chanselman
25. Hi-
I too am having the same issue. DNS:NR records have been updated and working properly. I have contacted aol.com via postmaster requests 3 times and 1 blog request. Still no response.
AOL please fix as soon as possible. Aol.com recipients are complaining
Thanks
Posted at 10:52AM on Mar 31st 2011 by Liz Crane
26. I am having the same issue with AOL although I am getting a slightly different block message(RTR:BB). According to AOL the RTR:BB message means that our SMTP server's IP address is a residential dynamic IP. Obviously it isn't a residential address, and I have double-checked with my ISP to be sure that it isn't somehow registered that way. My reverse DNS is also correct. I submitted my first "un-block" request more than a week ago with no response or resolution whatsoever. Our company corresponds with a lot of customers who use AOL and the issue is severely impacting our business. Please help, ticket numbers are below.
Support Request #2126 Confirmation - (3/25/11)
Support Request #1857 Confirmation - (3/23/11)
Posted at 8:53AM on Apr 4th 2011 by Danel Smith
27. Didn't receive email from support with tix number. Submitted 4th request to verify. I double checked spam filter, junk mail, ect.
Posted at 11:03AM on Mar 31st 2011 by Liz Crane
28. Found Tix Replies (2 tix numbers with 4 submitted)
#2246 3/28
#2114 3/25
Didn't receive reply on other two tickets.
Posted at 11:08AM on Mar 31st 2011 by Liz Crane
29. Thanks for looking into it. My initial ticket submitted on 3/18 was #1492 and ticket number #1712 submitted on 3/22.
Posted at 4:22PM on Mar 31st 2011 by Isaac
30. Same issue. #1833 on 3/23.
Thanks
Posted at 5:15PM on Mar 31st 2011 by Brook
31. Two tickets no response same problem. Glad to know I'm not the only one experiencing this. Tickets number #2419 and #2170.
Posted at 5:22PM on Mar 31st 2011 by Steve
32. two tickets also and, as everyone, no response : #1907 and #1483 (18/03)
thank you Margot for doing something
Posted at 6:05AM on Apr 1st 2011 by ddemblans
33. Ticket number 2435
Posted at 9:41AM on Apr 1st 2011 by Billy Mason
34.
HELP PLEASE!!!!
Same results as above..ticket 2396
Posted at 9:54AM on Apr 1st 2011 by rob
35. Same here, AOL is pathetic. They obviously don't care to let their customers receive mail. Our server has had proper rDNS for over 2 years and now it's being blocked. 421 4.7.1 : (DNS:NR)
AOL must have done something on their system. I've tried to submit a ticket like 10 times and never got a follow up with ticket number. This is beyond me.
Posted at 10:22AM on Apr 3rd 2011 by Shaun B
36. AOL... please stop this. Your customers deserve to get their legitimate mail.
Posted at 10:22AM on Apr 3rd 2011 by Shaun B
37. We too are having our business impacted by this issue. I've submitted three requests to fix and not received a response from any of them. We run guided tours overseas and this is costing me money. I'm having to track down my AOL customers and send them their documents, waivers, etc via snail mail. Can anyone say class action lawsuit?
Posted at 3:07PM on Apr 4th 2011 by Jonathan Lee
38. WOW! This is really crazy! AOL finally responded to me on 3/29/2011 (ticket #1392) and informed me that my IP was tagged appropriately and that the changes would be effective in 1-2 business days.
However, I'm still getting the DNS:NR error while trying to connect. AOL, please review and correct. Thanks.
Posted at 10:54PM on Apr 4th 2011 by cidljones
39. Same issue here for over 3 weeks now. Everything tests ok through AOL's tests, our rDNS is good, and we have no issues with any other domains.
Two support tickets in from our end:
#2395
#1816
Posted at 11:30AM on Apr 5th 2011 by RH
40. Margot-
Do you have an estimated time of when this issue will be fixed or when we will be contact? Most of us have been waiting for weeks. Is there another way we can escalate this issue.
Anything would be great.
Thanks Liz
Posted at 2:14PM on Apr 5th 2011 by Liz Crane