• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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