" All this is stating is that DNS++ does not support RFC 2671 EDNS protocol extensions. " DNS++ is responding per the RFC by sending the FORMERR back to the requestor. I believe this is OK. Maybe we don’t understand the issue?
DNS++ is apparently what we're using on our end. Is this behavior not according to the RFC? Aloha, Michael. -- Michael J Wise | Microsoft | Spam Analysis | "Your Spam Specimen Has Been Processed." | Got the Junk Mail Reporting Tool ? -----Original Message----- From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Carl Byington Sent: Thursday, April 28, 2016 12:03 PM To: mailop <mailop@mailop.org> Subject: Re: [mailop] DNS Errors for Microsoft Hostnames -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2016-04-28 at 11:41 -0700, Steve Atkins wrote: > Looks like (some of) the Microsoft authoritative servers are confused > by dnssec. > ~ ? dig +dnssec @ns1-proddns.glbdns.o365filtering.com pitt- > edu.mail.protection.outlook.com confused by edns: dig pitt-edu.mail.protection.outlook.com +edns @ns1-proddns.glbdns.o365filtering.com ;; WARNING: EDNS query returned status FORMERR - retry with '+noedns' See https://ednscomp.isc.org/compliance/summary.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlciXlAACgkQL6j7milTFsGSTwCfW2EsZWC7A/Pyv6ncUd6IbQ1f R20An10rS/a/rn6EZraiz1v1y86W0Bzi =m9M0 -----END PGP SIGNATURE----- _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
