?
Solved

Cannot send email to domain that used to be internal

Posted on 2009-04-29
8
Medium Priority
?
231 Views
Last Modified: 2012-05-06
One of our companies has repointed DNS for one of their domains to a site that is external to me. I used to have a local internal DNS zone for this that handled web and email for users that are inside the network, so I just deleted it. After flushing DNS, internal users can access the new website with no problem but when they attempt to send email to the new domain, they get an immediate bounceback from the internal Exchange server with error code 5.1.1 [SEE CODE]. It's almost like the Exchange server still thinks there is internal DNS for it, but I flushed DNS on the Exchange server and can access the website fine from there too. The email is never making it out of my network to my mail encryption appliance or spam / tls gateway.

Email from domains external to my local network flow to this "repointed" domain just fine.

I'm stumped.
address@domain.com on 4/29/2009 1:59 PM
            The e-mail account does not exist at the organization this message was sent to.  Check the e-mail address, or contact the recipient directly to find out the correct address.
            <internalmailserver.domain.local #5.1.1>

Open in new window

0
Comment
Question by:cowanbenefits
  • 6
  • 2
8 Comments
 
LVL 6

Assisted Solution

by:Steven Kirkland
Steven Kirkland earned 400 total points
ID: 24263791
Did you also restart exchange services or the server when you made changes to the DNS records?  It may seem reasonable to assume you've already done so but from what you've mention so far I'd just like to make sure you've done this as well.
0
 

Author Comment

by:cowanbenefits
ID: 24263866
I have not restarted Exchange services or the server. Restarting the server is not an option until much later in the day, but maybe I can try restarting Exchange services if it doesn't interfere too much with email connectivity. Thanks for the suggestion.
0
 

Author Comment

by:cowanbenefits
ID: 24268748
Neither restarting the services nor restarting the server fixes it. Any other ideas?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
LVL 6

Expert Comment

by:Steven Kirkland
ID: 24270920
host file on the server perhaps?  what happens when you ping the new server's FQDN from the exchange server?
0
 

Author Comment

by:cowanbenefits
ID: 24271068
There is nothing about that domain in the hosts file, and a ping to the domain from the Exchange server generates a reply from the correct external IP address.

This one is puzzling me... i bet it is something simple that I'm not thinking of. It seems like there must be something in Exchange that thinks that it is supposed to handle email for that domain.
0
 

Author Comment

by:cowanbenefits
ID: 24271723
Update: Figured out that there were still reverse DNS lookup records for the domain. Deleted those records out of the reverse lookup zones. Flushed DNS on Exchange server and client machine. It still doesn't work.
0
 

Accepted Solution

by:
cowanbenefits earned 0 total points
ID: 24273180
Update: Found a Recipient Policy for the domain in Exchange Recipient Policies that stated that the local exchange server was managing it. I deleted the recipient policy. Emails still don't go through but I have not restarted Exchange services yet.
0
 

Author Comment

by:cowanbenefits
ID: 24273206
Actually I guess it just took some time to refresh... now it is working. So the fix was to delete the receipient policy.  for the domain.
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to effectively resolve the number one email related issue received by helpdesks.
Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question