• 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.

Domain MX records missing, but show up correctly in Plesk

S

S.Mordziol

Guest
I tried searching all Plesk versions here in the forums for this, but did not find any clues. Also, the plesk help did not explain what I need to do in this case. Maybe someone can help?

I have one domain, hainlin.de with several domain aliases (like hainlin.com / knifemarket.com). I set all of them to synchronize DNS with primary domain and enabled mail and web access for all aliases. Then I created an email account ([email protected]), and set preferences for catch-all to go to that email address.

If I load up the webmail, I can send emails just fine - but sending an email to [email protected] from an external client like Gmail results in a delivery notification saying that it is an invalid address. Sending myself an email with the webmail works fine though.

In the plesk control panel DNS settings, everything seems fine:

217.160.18.137 / 24 PTR hainlin.de.
hainlin.de. NS ns.hainlin.de.
hainlin.de. A 217.160.18.137
hainlin.de. MX (0) mail.hainlin.de.
mail.hainlin.de. A 217.160.18.137
ns.hainlin.de. A 217.160.18.137
webmail.hainlin.de. A 217.160.18.137
www.hainlin.de. CNAME hainlin.de.

But if you use nslookup to find the MX record for hainlin.de, you don't get any results. Here is what I used inthe command window:

nslookup
set type=mx
hainlin.de

*** No Mail exchange (MX)-Records available for hainlin.de

How is that possible, and how can I possibly fix this?

Thanks a lot for you help!
 
Finally found the solution with the kind help of server tech support - there was an option in the server provider's control panel where you could set who should handle the IP's DNS records. It was set to using those of the server provider, not the server itself. I changed the option, and it worked nearly instantly.
 
Back
Top