550 5.0.350 and 550 5.4.312 errors with aarcnd.com

[katandcompany]

Hello,

We recently obtained aarcnd.com and configured it in Cloudflare. However, we have a 3rd party report that there are email issues with that domain, and they blame Cloudflare for it. In particular, they report the following messages:

• 550 5.0.350 Remote server returned an error → 550 Sender (aarcnd.com) has no A, AAAA, or MX DNS records
• 550 5.4.312 Message expired, DNS query failed(ServerFailure)

We’re not sure why those errors occur, as we have A and MX DNS records configured for the domain.

With that said, does anyone know why those errors happened and offer any advice for fixing them?

[wouter]

Hi katandcompany,

It’s possible the external party still had the previous nameservers cached, depending on when you switched them. I don’t see anything wrong otherwise.

[katandcompany]

Hi wouter,

Thanks for verifying the domain configuration. We’ll send this information to the 3rd party that reported the initial issue.

[katandcompany]

Hello,

There is something else brought to our attention. Is it possible the issue is caused by switching from one Cloudflare account to another Cloudflare account? Before last week, the domain was on a Cloudflare account with the nameservers chris.ns.cloudflare.com and emma.ns.cloudflare.com. It was then transferred to our domain registrar and configured on our Cloudflare account with the nameservers lisa.ns.cloudflare.com and walt.ns.cloudflare.com. If so, is there any way Cloudflare can issue a global DNS purge for the domain aarcnd.com to force other services to recognize the new nameserver values?

[wouter]

There’s no way for us to purge caches of external services unfortunately. However, caches should have expired automatically after 86400 seconds (24 hours).

[katandcompany]

That’s what we thought. It was the 3rd party reporter that was wondering about that.