Problems sending Mails to 1&1, United Internet, Schlund, etc. (DE) - snwlhostedeu.com
Hi guys,
a HES (EU) customer is having trouble sending mails to customers who have their domains running with the probably market leading Providers 1&1 United Internet and their subbrands, like Schlund etc.
All Mails addressed to one of the domains get bounced with smtp;550 Requested action not taken: mailbox unavailable invalid DNS MX or A/AAAA resource record.
This message is confusing, it's either mailbox unavailable or invalid, can't be both, IMHO.
Message to other recipients are going through without trouble, the affected domains were working just find 2 days ago.
Anyone is having this as well and already reported it?
--Michael@BWC
Answers
Hi Michael,
same for me :(
The issue started yesterday a 4pm. CEST for my customer.
Details
Error: 550 5.4.350 Remote server returned invalid or missing DNS MX or A record for recipient domain -> 550 invalid DNS MX or A/AAAA resource record
Remoteserver: euprodsharedou.com.snwlhostedeu.com
Regards,
Daniel
Just in case the support "never" heard about the problems, I opened Case #43666998 about the United Domains dilemma, and Case #43667007 about the incorrect configuration of the zone snwlhostedeu.com with a non resolvable NS for sjl0vm-heswd01.colo.sonicwall.com, which might cause problems resolving your own MX or HES connector.
--Michael@BWC
We´re having the same issue with all our HES customers.
I guess there´s nothing we can do but wait for the backend team to fix it..(as always with HES).
We hope for the worst and fear the best, or was it the other way around? 🤪
--Michael@BWC
Ticket #43666998 (United Internet comains) got escalated, status.sonicwall.com does not show anything.
Thank you for contacting Sonicwall support. We have escalated this issue and escalation team is working on it. We will keep you update with further details.
You can subscribe on status.sonicwall.com to get latest updates.
Apologize for the inconvenience.
--Michael@BWC
The whole thing might be not just limited to United Domains, another delivery to a different provider got bounced with this message:
It might be all related to the wrongful configuration of the NS records for snwlhostedeu.com (and snwlhosted.com).
--Michael@BWC
Situation seems to be defused, at the end it might be caused by a small DNS misconfiguration at SNWL.
--Michael@BWC
I'am confused, did SNWL really revert back to the DNS misconfiguration and everything will start all over again? BTW, same goes again for snwlhosted.com
@David W any take on that?
--Michael@BWC