Office 365 MX record issue

Justin Time

New member
Joined
Aug 4, 2020
Messages
3
Greetings

This is my first day using DirectAdmin, so apologies in advance if I lack some understanding.
I am trying to add an MX-record in DirectAdmin so mail gets routed to Office 365, but I face some difficulties.

For some reason, the "Name"-field seems to require "domain.com.", however, Microsoft specifically tell me to put "@" in Name-field.
When I put "domain.com." in Name-field, Office 365 complains.

I have seen this thread: https://forum.directadmin.com/threads/configuring-dns-to-use-office-365.44058/#post-234190
I then tried with following settings:
Name: domain-co-uk.mail.eo.outlook.com. (with own domain). TTL: 3600 Type: MX Priority: 0 Value: 0

With this setting, Office 365 gives me the "missing record"-error.

When I try with "domain.com." in Name-field, it complains on the value, which then shows up like this in Office 365: domain-co-uk.mail.eo.outlook.com.domain.com - as you can see, it adds "domain.com" at the end, and Office 365 complains.

I also unchecked the "Local mail server".

Anyone who are able to help me?

Best regards,
Eric
 
Why not used the automatic option?

I also unchecked the "Local mail server".
This is on the seperate MX records page isn't it? There is also the option to setup the external mailserver.
There is the line: "Select your remote email provider ". You can select Microsoft 365 there.

Alle records including the autodiscover record are made then automatically.
Also the SRV records are created automatically and others used for lync.com which might be needed.
 
Thanks to all who responded to this and similar posts.
I had a similar problem this morning. Eventually I deleted all the manual entries, and just clicked on the automatic option within 'Modify MX Records'.
This was for Microsoft 365. The entries that show up using automatic are very different from those that Microsoft instruct you to use.
The automatic option is working.
 
Back
Top