Rose, Scott wrote:
outlook.com isn’t signed, so I doubt it is a DNSSEC error (though they
look the same). BIND should see that it isn’t signed and just roll
with it. Could be that a server in the chain isn’t responding
(whatever serves the mail.protection.outlook.com zone).
We use Office365 too, and have heard the same problem from people
trying to send us mail, only they have been seeing NXDOMAIN errors for
names in protection.outlook.com, not SERVFAIL. That was a few months
ago and haven’t seen the problem again.
Hate to say this but it could also be a zero day... I had similar
reported about SORBS.net (infact both the FreeBSD and
chilli.nosignal.org list services suspended me because of DNS errors.. -
both reported an issue with AAAA records - and I don't have DNSSec or
AAAA records for SORBS)
Maybe someone cleverer than me can poke around the errors with that in
mind...
Regards,
Michelle
--
Michelle Sullivan
http://www.mhix.org/
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
