We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
COURSE of the MONTH
12 days, 17 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Email Bounce Messages
Posted on 2013-12-16
Hello,
A client was moved from a on-premise Exchange environment over to a hosted cloud service and some senders are getting NDR messages stating their AAAA record isnt correct.
This is the message:
#< #5.4.4 X-Postfix; Host or domain name not found. Name service error for name=mail.oldemailserver.c
X-FFO-Routing-Override: oldemailserver.com%mail.ol
Their current setup allows email to flow to a cloud spam filter service then shoots over into the hosted mail platform via smarthost.
I have yet to hear back from my cloud filter service but I'm thinking they're not ready for an IPv6 RR.
I'm just thinking that the email source records need to be updated (dns flush). Would someone confirm this hypothesis or point me in the right direction please?
A client was moved from a on-premise Exchange environment over to a hosted cloud service and some senders are getting NDR messages stating their AAAA record isnt correct.
This is the message:
#< #5.4.4 X-Postfix; Host or domain name not found. Name service error for name=mail.oldemailserver.c
X-FFO-Routing-Override: oldemailserver.com%mail.ol
Their current setup allows email to flow to a cloud spam filter service then shoots over into the hosted mail platform via smarthost.
I have yet to hear back from my cloud filter service but I'm thinking they're not ready for an IPv6 RR.
I'm just thinking that the email source records need to be updated (dns flush). Would someone confirm this hypothesis or point me in the right direction please?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2 Comments
Whether they are ready for IPv6 or not, you can prevent this by removing references to IPv6 host names in your DNS Zones. This will not hinder your mail delivery in any way but it can obviously cause unexpected issues.
It look like sender Public DNS still holding your old email domain records.
Could you go to www.centralops.net do nslookup for your email address. Verify if the information e.g. MX and A records pointing to correct information such pointing to new hosted cloud service.
Could you go to www.centralops.net do nslookup for your email address. Verify if the information e.g. MX and A records pointing to correct information such pointing to new hosted cloud service.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Find out what you should include to make the best professional email signature for your organization.
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Recipients >> Sha…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync.
To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses
Course of the Month12 days, 17 hours left to enroll
777 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.