On Tue, Aug 25, 2015 at 11:28:27AM -0700, Periko Support wrote:
> Aug 25 08:23:57 mail postfix/smtp[21291]: warning: no MX host for
> XYZ.com has a valid address record
> Aug 25 08:46:08 mail postfix/smtp[22177]: warning: no MX host for
> XYZ.com has a valid address record
> Aug 25 09:19:18 mail postfix/smtp[23290]: warning: no MX host for
> XYZ.com has a valid address record
Is "xyz.com" the actual domain, or did you "anonymize" it?
$ dig +noall +ans +nocl +nottl -t mx xyz.com | sort -k3n
xyz.com. MX 1 aspmx.l.google.com.
xyz.com. MX 5 alt1.aspmx.l.google.com.
xyz.com. MX 5 alt2.aspmx.l.google.com.
xyz.com. MX 10 aspmx2.googlemail.com.
xyz.com. MX 10 aspmx3.googlemail.com.
But of course all those Gmail MX hosts do have IP addresses.
> Aug 25 10:26:08 mail postfix/smtp[29046]: 36E361B0063:
> to=<u...@xyz.com>, relay=none, delay=7341, delays=7331/0.01/10/0,
> dsn=4.4.3, status=deferred (Host or domain name not found. Name
> service error for name=inbound.registeredsite.com type=A: Host not
> found, try again)
However, your MX host with no IP address is not one of the above,
so you're wasting our time obfuscating the key piece of factual
data, namely the problem domain name.
Mind you, even that host also has an IP address:
$ dig +noall +ans +nocl +nottl -t a inbound.registeredsite.com
inbound.registeredsite.com. A 64.69.222.10
So it seems your DNS resolver is not terribly reliable, or that
domain was having some problems that are now resolved.
--
Viktor.
