Problem receiving Email from outside our domain

A few months ago we added an Exchange 2010 Server to our existing Exchange 2003 Server enviorment. This week I removed the Exchange 2003 server and transferred the OAB and public folders over to the new Exchange 2010 server. Since the routing group connector is removed on the removal I also put in a request to our ISP to update our MX record to reflect the Exchange 2010 as the incoming mail server and to remove the old MX record for the 2003 server. I have not been able to receive any email from the outside world since I removed the old Exchange server and updated our MX record. I have check with MXToolbox and it shows that our MX points to our new server name and the PTR record also exist. When I got to Gmail or Yahoo to send to my inside email I get an error that we have no DNS records and the message fails. I cant find what could be wrong in my configuration and any support you could provide would be helpful.
johnrkeanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
Recreate the receive connector. And read this
http://www.petri.co.il/forums/showthread.php?t=42794
0
tomotCommented:
you mention "I also put in a request to our ISP to update our MX record to reflect the Exchange 2010".
Does this mean that your Exchange 2010 is on a different public IP than your Exchange 2003 was?

If your Exchange server, the new and the old, were on the same LAN or DMZ behind a firewall. you would not need to change your public MX. You would just need to reconfigure your firewall to NAT your public IP form the old Exchange to new Exchange.
0
AmitIT ArchitectCommented:
@tomot
You are right, I don't think MX change is required at all. I assume again DNS replication takes 3 days minimum to replicate around the world.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

johnrkeanAuthor Commented:
I would appear that our mx record is working for some domains to send but not others. I tested gmail and hotmail and was able to send but yahoo.com returns a dns record error. Also this could be dns related since I just went to intodns.com and found when I run my domain beaumontusd.k12.ca.us I get some errors. But I am unsure how to correct them.
0
tomotCommented:
Well, if that is the case, sending emails from some domains work, then you probably did change your public IP, put in the MX change request, and not it is slowly propagating to all DNS server around the globe. The propagation could take up to 4 days in some cases, but with some large email providers like gmail or yahoo, that change should happen within 24 hours...
0
johnrkeanAuthor Commented:
In reguards to tomot: Question, Yes, the outside IP of the incoming mail server did change. It also has a PRT record. The hostname is bmntex1.beaumontusd.k12.ca.us.
0
tomotCommented:
is this your new Public IP?
65.208.173.218
If it is, than you should be OK, it just takes time to update all DNS servers. I checked, and you SMTP server config looks fine...
> set type=mx
> bmntex1.beaumontusd.k12.ca.us

bmntex1.beaumontusd.k12.ca.us   MX preference = 10, mail exchanger = bmntex1.beaumontusd.k12.ca.us
bmntex1.beaumontusd.k12.ca.us   internet address = 65.208.173.218
>

Open in new window

0
tomotCommented:
Here is a validation to my previous statement, it takes time. I did 2 different checks and go 2 different IPs probably you old and your new IP. Not all DNS are updated yet..
Check1
Check2
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tomotCommented:
never mind, the second screenshot IP is probably a source IP. (mxtoolbox.com)
0
johnrkeanAuthor Commented:
Great, It does seem to be taking a bit long since I submitted the records early Monday morning and still many domains are still not finding our dns records. Since you think everything looks good on my end I may just need to wait a little longer for the records to propagate to the rest of the world. Thank you for all the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.