My MX record test is passing:
Actually, your MX record is unusually configured, so the presumed "pass" should be taken with a grain of salt.
mxlogicmx.net seems to be aliased to mxlogic.net. What's the point in that? It appears that the mxlogicmx.net domain is not actually used anywhere.
Additionally, the MX records for mxlogic.net seem to be unusually named:
mxlogic.net.inbound15.mxlogic.net
mxlogic.net.inbound25.mxlogic.net
I'm inclined to think there's a missing terminal period in the zone MX records for these entries.
Beyond that,
mxlogic.net.inbound15.mxlogic.net has FOUR different IP Addresses assigned to that hostname (208.65.144.12, 208.65.144.13, 208.65.145.12, and 208.65.145.13)
=and=
mxlogic.net.inbound25.mxlogic.net has only one IP Address (208.65.145.11)
All connections to Mailservers port 25 have failed.
Ostensibly those IP addresses are not answering the phone! Or the confusion of the myriad of domains and hostnames is a contributing factor.
In independent tests to all five identified IP Addresses on port 25, I received these results:
- mxlogic.net.inbound15.mxlogic.net (208.65.145.11) is answered by p02c12m081.mxlogic.net
- mxlogic.net.inbound25.mxlogic.net (208.65.144.12) is answered by p02c11m072.mxlogic.net
- mxlogic.net.inbound25.mxlogic.net (208.65.144.13) is answered by p01c11m083.mxlogic.net
- mxlogic.net.inbound25.mxlogic.net (208.65.145.12) is answered by p02c12m105.mxlogic.net
- mxlogic.net.inbound25.mxlogic.net (208.65.145.13) is answered by p01c12m105.mxlogic.net
So my first suggestion would be to update ALL of your DNS records to use **CANONICAL** names rather than aliases.
The ONLY place aliases should be used is in CNAME records.
Once you've corrected the DNS records to point to the actual names of real machines... try DNStuff again.
As for 54.235.159.97 .... that's an Amazon AWS address, so you tell me: How does Amazon AWS fit into this scheme?