G DATA 365 | Mail Protection
Set your domain’s MX record to G DATA 365 | Mail Protection
|
Before making changes to the MX record for your domains, please read the Setup guide for the product launch G DATA 365 | Mail Protection and follow the Notes on using the connector and the rule. |
A general guide for all Customers is not possible here. There are too many different configurations and too many places where domains are managed.
First, it is important for you to know where your domain is managed (not to be confused with the place where the domain is hosted). If you do not manage DNS in your in-house IT department and do not know where the MX record needs to be changed, you can find DNS lookup tools on the Internet. With the help of such tools, you can determine the DNS management provider for your domain. Your web host’s support team may also be able to assist you in some cases.
Using our fictitious Customer x-company as an example, we explain here how the MX record must be set correctly. You can apply this example to your management provider, adapted to the interfaces there.
Our fictitious Customer has a domain named x-company.cloud, which is managed at IONOS. When Microsoft Exchange Online was set up, this domain was connected to Microsoft Exchange Online. The domain setup at IONOS was carried out automatically by Microsoft.
1. |
First, our fictitious Customer logs in to their account. Show IONOS example screenshot
|
2. |
Then they look for the location where they can edit the DNS records for their domain. Show IONOS example screenshot
|
3. |
The DNS set up by Microsoft then looks like this: 
|
4. |
There, they change the MX record to: mailprotection.gdata.de After saving, IONOS deletes all other records created by Microsoft. 
|
From now on, all emails to x-company.cloud are first sent to our G DATA 365 | Mail Protection.
Finding the DNS records to be entered manually in the Microsoft admin center
So that the DNS for Microsoft Exchange Online is correct again for our example Customer, the DNS records removed by IONOS must be added again manually. Otherwise, their Outlook clients can no longer connect to Microsoft Exchange Online.
In the Microsoft Admin Center, error messages are already displayed after the changes to the DNS:
1. |
By clicking the domain and the DNS records tab, our example Customer switches to the DNS overview page in the Microsoft admin center. 
|
2. |
There, all DNS records required by Microsoft are displayed with an error. It is correct that an error is displayed for the MX record due to the change in Microsoft Exchange Online, and it can remain as is. In our example, the yellow-marked records under the Exchange section (TXT and CName) must be entered at IONOS. The orange-marked records (CName) only need to be entered in certain cases (e.g., when using Microsoft Intune and Android). 
|
Entering the required DNS records using IONOS as an example
1. |
If the window has already been closed, they log in to their account again. Show IONOS example screenshot
|
2. |
Then they look for the location where they can edit the DNS records for their domain. Show screenshot
|
3. |
They click Add record. Show screenshot
|
4. |
They select which record type they want to create. You can find this information in the first column of the DNS overview page at Microsoft. Show screenshot
|
5. |
They enter the details from the DNS overview page at Microsoft: name, value, and TTL. Show screenshot
|
6. |
They save the details by clicking Save. |
7. |
Then they repeat steps 4–6 for all required DNS records. Show screenshot
|
The relevant DNS records should be displayed with status Ok on the DNS overview page at Microsoft.
