Algunos de los destinatarios no recibieron su mensaje.
Asunto: OPENVPN+RADIUS+MFA issue
Enviado el: 17/06/2026 13:08
No se puede localizar a los destinatarios siguientes:
'support@mikrotik.com' en 17/06/2026 13:09
Error del servidor: '450 4.1.2 <[support@mikrotik.com](mailto:support@mikrotik.com)>: Recipient address rejected: Domain not found'
I send email to mikrotik.com and receive this error, is a temporal error?
@normis
SOMETHING'S NOT WORKING...
DNS broken, so no MX solved...
I can access Mikrotik site from local now but from GitHub Actions cann't. Scripts fails from last night.
$ for server in dns.google 1.1.1.1 9.9.9.9 208.67.222.222; do date -uR && echo -e "\n\n# === ${server} ===\n" && host mikrotik.com "$server" ; done
Wed, 17 Jun 2026 13:33:35 +0000
=== dns.google ===
Using domain server:
Name: dns.google
Address: 8.8.4.4#53
Aliases:
mikrotik.com has address 159.148.172.205
mikrotik.com has IPv6 address 2a02:610:7501:2000::205
mikrotik.com mail is handled by 20 mailgw-b.mt.lv.
mikrotik.com mail is handled by 10 mailgw-a.mt.lv.
Wed, 17 Jun 2026 13:33:36 +0000
=== 1.1.1.1 ===
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
mikrotik.com has address 159.148.172.205
mikrotik.com has IPv6 address 2a02:610:7501:2000::205
mikrotik.com mail is handled by 20 mailgw-b.mt.lv.
mikrotik.com mail is handled by 10 mailgw-a.mt.lv.
Wed, 17 Jun 2026 13:33:36 +0000
=== 9.9.9.9 ===
Using domain server:
Name: 9.9.9.9
Address: 9.9.9.9#53
Aliases:
mikrotik.com has address 159.148.172.205
mikrotik.com has IPv6 address 2a02:610:7501:2000::205
mikrotik.com mail is handled by 20 mailgw-b.mt.lv.
mikrotik.com mail is handled by 10 mailgw-a.mt.lv.
Wed, 17 Jun 2026 13:33:36 +0000
=== 208.67.222.222 ===
Using domain server:
Name: 208.67.222.222
Address: 208.67.222.222#53
Aliases:
mikrotik.com has address 159.148.172.205
mikrotik.com has IPv6 address 2a02:610:7501:2000::205
mikrotik.com mail is handled by 20 mailgw-b.mt.lv.
mikrotik.com mail is handled by 10 mailgw-a.mt.lv.
Algunos de los destinatarios no recibieron su mensaje.
Asunto: OPENVPN+RADIUS+MFA issue
Enviado el: 18/06/2026 10:07
No se puede localizar a los destinatarios siguientes:
'support@mikrotik.com' en 18/06/2026 10:07
Error del servidor: '450 4.1.2 <[support@mikrotik.com](mailto:support@mikrotik.com)>: Recipient address rejected: Domain not found'
This morning I checked again, and according to mxtoolbox.com, the mikrotik.com domain has no DNS servers, and my emails are still being returned because the domain doesn't exist.
I'm surprised that no one at mikrotik.com has noticed anything or fixed this. It's a serious problem that the MX servers have disappeared, but it's even worse that no one at Mikrotik has detected and fixed it.
It seems like a problem of mxtoolbox. Other services can resolve MX using authoritative dns server without issues.
Confirmed with Microsoft Remote Connectivity Analyzer.
Testing inbound SMTP mail flow for domain 'support@mikrotik.com'.
The Microsoft Connectivity Analyzer failed to test inbound SMTP mail flow.
Additional Details
Elapsed Time: 16094 ms.
Test Steps
Attempting to retrieve DNS MX records for domain 'mikrotik.com'.
The Microsoft Connectivity Analyzer wasn't able to retrieve MX records from DNS.
Tell me more about this issue and how to resolve it
Additional Details
No MX records were found in DNS for SMTP domain 'mikrotik.com'.
Elapsed Time: 16094 ms.
RCATestResult.zip (6.7 KB)
It's not just MXTOOLBOX that's failing; from my email provider, piensasolutions.com, it's also impossible to send emails to mikrotik.com. It's very strange; why do some providers resolve the issue while others don't?
I sent the email from my personal gmail.com account and it seems to have gone through correctly. This is VERY strange, why do some providers not have an MX record and others do from mikrotik.com???
Reply received by JIRA
Because DNS seems to be broken/working intermittently.
If you try long enough the other provider should be able to deliver your mail 
Mikrotik's authoritative DNS server is misconfigured and returning conflicting nameservers vs what is registered at the .com registry.
The problem was, Mikrotik's authoritative servers were only responding to Google, Quad9, Cloudflare and some other well known public recursive DNS service.
In addition to that they have conflicting NS records, different from the ones in the WHOIS record.
They fixed the auth DNS server access problem yesterday.
yes it was a short issue on our side, and was fixed yesterday, sorry about the inconvenience
Thank you for resolving the issue. I have already opened a support ticket regarding the OpenVPN+MFA problem and timeout from my corporate email.
