Strange MX records issue

After pointing the MX records to Office 365, the email is not flowing anymore.

When I do a "Find and fix issues" in the Office 365 portal, I get this error:

Capture.PNG

The MX records are clearly not setup this way at the DNS registrar.

I'm not sure if it's clear from the picture but basically it says that the domain is added at the end one more time.

Any help would be appreciated.
Alan DalaITAsked:
Who is Participating?
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.

KimputerCommented:
I think YOU really did set it up wrongly. Probably because your DNS registrar web interface allows you to fill in servers BEFORE the domain name. (usually a text block, and behind it the domain name your administrating, as that's usually what is expected in this admin panel).
If there's no way to have FULL freedom to fill in your DNS settings, just get in touch with support (either they will show you how to fill in an entry unrelated to your own domain name, or they will manually add it for you).
It's quite logical though. DNS admin panels are designed to make it easy for you to add entries for
mx.domain.com
server1.domain.com
server2.domain.com
where you fill in only the first part, to help you minimise making typos. In this case though, you need to get outside this ease of use parameters.
To double check that your MX record is really wrong, you can do a nslookup against google's dns 8.8.8.8 and see that you're really wrong.
0
Leon KammerCommented:
Hi,

Microsoft put out a statement earlier in the year regarding this.

All domain specific MX records must be changed to
yourdomain-tld.mail.eo.outlook.com or
yourdomain-tld.mail.protection.outlook.com to avoid service flow disruption.

IIRC this was sometime around July.

Also ensure that you have set the spf correctly

"v=spf1 include:spf.protection.outlook.com -all"
Cheers

Leon
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
Alan DalaITAuthor Commented:
I forgot to add the .(dot) after com. WOW! Some DNS providers need that .(dot), some not.


Thanks everyone for 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
DNS

From novice to tech pro — start learning today.