On 26 Jan 2021, at 11:38, Viktor Dukhovni wrote:
On Tue, Jan 26, 2021 at 10:46:04AM -0500, Ruben Safir wrote:
I am getting this strange rejections to talk to NYC government
[...]
On Tue, Jan 26, 2021 at 11:04:39AM -0500, Bill Cole wrote:
dig mx2.nycdoitt.iphmx.com
[... list of A records snipped ...]
Assuming that the "Diagnostic-Code" field of the rejection message is
in
fact the real reason for the failure and not doing something thatb
mimics DNS failure or tells outright lies, this indicates that their
DNS
resolver is broken.
Whose DNS resolver?
The system generating that "Diagnostic-Code" field claiming that
resolution isn't working for the perfectly resolvable Ironport name.
I missed that the name is an MX for the recipient address, rather than
the name of the machine trying unsuccessfully to pass along the message,
i.e. based on the opening line I thought that the error occurred while
"talking to" the next hop.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
