Office 365 Exchange Godaddy Setup Issues

What's the TTL for your DNS zone / records?  It seems plausible enough that this is what's happening:

- You made the DNS change, but MX records were previously resolved / cached.
- You send a test message from _____, it resolves incorrectly to deliver to the GoDaddy server.
- GoDaddy's MX receives the message, with authoritative access to your DNS zone, and bounces the message to MS.
- One of the MX's at MS has previously routed mail to your domain (first bullet), and cached resolution.
- It kindly forwards the message to GoDaddy as it believes is appropriate.  Repeat.

The steps may happen in a different order, but this seems as it may be what's causing the routing loop.  If this is the case, and your mail is properly registered / configured for Office 365, when the TTL expires the issue would likely go away.  You may be able to predict how long this would take by reviewing the time to live (TTL) for your DNS zone / records.  As for migrating your mail, once you're connected to your profile in 365, you should be able to move mail from your PST (previous POP config).  Best of luck!

office 365 will not inter operate with other email services.  You need to set up your office 365 account like a brand new account, using only the office 365 dns and other host records.  then you can migrate your email from the godaddy servers to the 365 servers using migrationwiz.com to do a cloud to cloud migration.  Office 365 can only be in a hybrid email scenario with exchange 2010 premise based, its not supported in any other configuration.  Ive done this exact migration from godaddy email to 365 before and this is the only way it will work perfectly.  What 365 plan do you have?

I signed up for the Exchange only ($4/seat) plan. The TTL is 1HR as 365 instructed. Maybe I wasn't clear that I want this to be shared with GoDaddy so at first I put in the 0 record to point to 365 and left the 10 record to point to GD. When that didn't work I took out the 10 record all together.

Justin: do I need to take out the email records that point to GD under CNAME? I would still like to be able to use GD webmail in a pinch, but that is not a requirement. That's why I set 365 to shared.



ORIGINAL GD DNS Records


Here is what 365 told me to add to GD DNS:


I did not take out anything except the extra MX record when I tried to set this up.

Thanks for the help, this is way above my paygrade!

It sounds like you want to be able to send and receive email from godaddy email services and office 365 at the same time.  Am I correct?  If so this is not possible,  I would delete any and all records that pertain to godaddy email and keep the 365 dns,  office 365 is the exchange 2010 platform hosted, its 100x better than any mail server you're going to use.  you dont want 2 mx totally different mx records, this means mail could go to godaddy sometimes then to 365 sometimes, I actually dont think it will even work.  You can have multiple MX records if they both are pointing to the same server not just random services.

Thanks for the tip. I will try this over the weekend. I don't want to lose anymore mail as I change the MX record.

To clarify: I should remove the following from the CNAME


Thanks again, I will report back.

yes remove any and all godaddy email records and just use the 365 records and youll be golden

Thanks - will report back.

Sorry for the delay.

Saturday I changed my GD settings to:


Still got the too many hops error. Very frustrated. Can I just forward my mail from GD to 365? If so how do I set 365 to send through GD (as I don't want my new 365 email address visible to anyone getting or sending email to me).

Sorry to be a pain, but I am about to just cancel the 365 and go back the way I was!

I have the "Exchange Online Plan 1".

I want only the email plan. I have this  website is redirecting to my main website site.

When I "WHOIS" the A record I get: pwfwd-v01.prod.mesa1.secureserver.net

Should I remove the A record all together? Will this screw up the forwarding?

Sorry for the questions, but you seem to have the answers!

Thanks again.

ok in the plan that you have the plan 1. the only records you need in place are the 3 records I said above.  the A record you have inplace looks like its for godaddy email, so you can delete it.  anything with the secureserver.net in the address is godaddy.  

Now your asking if it will screw up the forwarding, what exactly are you trying to forward?

I thought you just wanted to use office 365 email.

Here is my convoluted setup:


Most of my mail still goes to XYZ.net which is why I wanted the 365 exchange.

Again, pardon my ignorance and many thanks for the help

ok i get it.  as far as people going to the new website with the old address theres a record called a URL redirect record which takes of the website redirection.

Now because you still receive email from both xyz.net and xyz123.com. what you can do is add both domains to the office 365 account and then you can receive email on both domains with an email alias.  We have clients that have this they had an older domain and a newer one and they needed to receive email from both and office 365 allows this to happen.  Under the admin account for 365 is where you add the domains just add both for email and your good to go.  Nothing changes as far as the DNS records you need to add to godaddy. Exactly the records i said to add above are still the only records you need.

Thanks, I'll give it a try.

I'm nominating you for Sainthood!

thanks, if you reward the points soon I appreciate it. also would be nice if you could vote my article on office 365 helpful.  thanks

https://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Microsoft_Office_365/A_10355-Microsoft-Office-365-Demystified.html

I'll give the points just for persistence! Will also vote. Thanks again.

Thanks for your extended communication with me.