• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved DNS problems with Offices 365

Mikelug

New Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
Plesk Obsidian v18.0.54_build1800230824.08 os_Ubuntu 20.04
Good morning, until two days ago we had the mail of our domains working with Office365 and our Plesk server acted as DNS for these domains, but yesterday we started to not receive some emails randomly, the solution that we have come has been to use our domain provider as DNS server after this change the mail service restored to normal.
We have also looked in the log file /var/log/messages and there is nothing, it is empty.

What problem could be causing this situation?

Thanks.
 
It's hard to find out now that the configuration was changed. Was bind running and resolving names correctly? If nothing has changed on the server, you could still query that server for a name resolution of the MX record of the domain. If it is still on the server, bind will respond when you query it directly with nslookup or dig. Another reason could be that the Office account did not receive mails temporarily. Sometimes MS has that issue, rarely, but it occurs. It normally fixes itself after a few hours, but sending servers may not re-send the mail immediately so that you get the impression it was not sent at all.
 
Good morning, sorry for the delay, it seems it was a temporary problem with Office, thanks for the quick response.
 
Back
Top